#
Unify Automations
Logo
Setup Triggers
Logo
Callable

Callable

Logo

10 mins READ

Overview

Callables by UnifyApps enable the creation of reusable automations that can be triggered externally via APIs or from other automations.

"It allows you to seamlessly integrate with third-party systems, support dynamic automation selection based on runtime conditions, and implement conditional execution based on trigger parameters."

Image
Image

Key Features

  • Initiate automation via external API calls: Expose Automations via an API Endpoint that can be called from external systems. Explore more regarding API Endpoint creation here.

  • Trigger child automation from parent automation: Allows you to build automations that can be called from other automations. It helps to create repeatable sets of actions that can be reused in other automations.

  • Create standardized interfaces for modular automation design: Establish consistent input/output structure for your automations and drastically reduce the time taken to configure and maintain the callable automation.

  • Enable dynamic automation selection based on runtime conditions: Create automation that can choose and execute different automation (interface based) in real-time, based on changing variables or user inputs

Use Case

API Integration for Data Processing:

Let’s consider if you want to search a ticket in Zendesk, create a Salesforce case if the ticket exists in Zendesk, and then expose it as a REST endpoint.

Anyone can use this endpoint to access and consume data without requiring access to the UnifyApps Account.

  • Start by creating automation with “Call Automation via API” as a trigger.

  • Define the request and response structures for the endpoint by defining the API request trigger parameters required for searching a ticket in Zendesk.
    For example: Email address or ticket ID

    Thumbnail

    Refer

    Refer to this article to know more about configuring request and response structure.

    Image
    Image

  • Select the “Get ticket details by ID” action in Zendesk and map the “Ticket ID” to the “Call Automation via API” output.

  • If the ticket exists then create a Case in Salesforce using the “Create Record” action in Salesforce. 

  • Select the “Respond to API request” action to ensure our API endpoint returns a response that indicates if the actions were successful.

  • In the Response Schema section, map the appropriate data to the schema fields.

  • For example, we want to return the created Case’s ID in the response, so we'll map our response field to the Case ID datapill returned from the Create record in Salesforce action.

    Image
    Image

Detailed Breakdown

API-based Callable

API-based callables allow you to trigger automation through external API requests.

Thumbnail

Refer

You can read more about API-based callable here.

Callable from Another Automation

Allows you to build automations that can be called from other automations.

Thumbnail

Refer

You can read more about Callable from Automation here.

Interface-based Callables 

It allows you to create standardized interfaces for your automation, enabling dynamic selection and execution of automations based on conditions.

Thumbnail

Refer

You can read more about Interface based callable here.

FAQs

Is there a limit to how many child automation I can call from a parent? 

While there's no hard limit, keeping the number of nested calls reasonable for performance and maintainability is recommended.

How do I handle authentication for API-based callables? 

You can implement various authentication methods using request headers. Common approaches include API keys, OAuth tokens, or custom authentication schemes. Ensure you follow security best practices when handling authentication.

Can I use callables to integrate with external systems that have rate limits? 

Yes, you can implement rate-limit Policy while configuring the API in the API manager. For more information refer to API policy.

How do I debug complex automations involving multiple callables? 

UnifyApps provides logs of every run for automation which provides you the node where you have encountered the Error. For more information refer to Runs.