Unify Automations
Logo
Build your first automation

Build your first automation

Logo

5 mins READ

Unify Automations lets you connect apps, schedule tasks, and run logic without writing backend code — you wire triggers to actions on a visual canvas, and the platform runs your workflow.

Overview

An automation has two parts: a trigger (the event that starts the run) and one or more actions (what happens in response). Triggers listen for something — a new record, an API call, a schedule — and actions do something with that signal: send a message, update a record, run code, branch on conditions.

build_your_first_auto_2_1.png
build_your_first_auto_2_1.png

Trigger Types

Trigger

What starts the run

Key detail

App Trigger

An event in an external app (new Gmail thread, Zendesk ticket updated, Salesforce record created)

Subscribe to app events; no API call needed

Callable

Another automation or an API call invokes this one

Use when you need to send a response back to the caller

Webhook

An HTTP request to the automation's generated URL

Sends a 204 response by default for all successful runs

Schedule

A recurring interval (every N seconds, minutes, hours, days, weeks or months) or a cron expression

No external event required

Action Types

Actions are grouped into three categories in the node picker:

Logic tools — control flow within the automation:

  • Condition — branch on a true/false test

  • Branch — multi-path routing

  • Loop — iterate over a list

  • Delay — pause execution for a duration

UnifyApps actions — built-in platform capabilities:

  • Storage by UnifyApps — read and write to key-value or structured storage

  • Variable by UnifyApps — set and get variables scoped to the run

  • Code by UnifyApps — run JavaScript, Groovy, Python, or Java inline

Connector Actions — app-specific operations (Create record in Salesforce, Post message in Slack, and so on). The list updates as new connectors are added.

How to Create a New Automation

  1. Log in to your UnifyApps account.

  2. Navigate to the Automations section within Unify Automations.

  3. Click New Automation in the top right corner. The Describe. Build. Automate screen opens.

  4. Describe what you want to automate and let AI generate it, or choose Create manually and enter a Name, optional Tags, a workspace and a short description.

  5. In the builder, select the trigger and configure its Setup.

  6. Click the + button below a step to add an action.

  7. Configure each action's settings and inputs.

  8. Test your automation using the built-in test module.

  9. Save your automation, then click Deploy to make it Live.

Notes

Unify Automations supports every pattern from simple one-step notifications to complex multi-branch workflows with loops and callable sub-automations. To make the most of it:

  • Start with the trigger type that matches your source event — app trigger for app events, Schedule for time-based, callable for API-driven flows.

  • Use Variable by UnifyApps to pass data between non-adjacent nodes without re-querying an external API.

  • Test before deploying — the built-in test module runs a single instance with hard-coded input so you can inspect each node's output before the automation goes live.

  • Keep automations focused on one business process; chain them via Callable triggers instead of building one automation that does everything.

FAQs

How do I choose the right trigger?

Match the trigger to what should start the workflow. Use a connector-based trigger when an app event (new email, record created) should kick things off. Use Callable when another system or automation will invoke this one via API. Use Schedule for time-based recurring work.

Can I combine multiple triggers?

No — each automation has exactly one trigger. If you need the same logic to start from multiple events, create separate automations that each call a shared Callable automation.

Is there a limit to the number of actions I can add?

No. You can add as many actions as your automation logic requires. Automations with many sequential steps are valid, though deeply nested loops may affect performance.

How do I test my automation before deploying it?

Use the Test section in the automation builder. Click "Start New Test", provide input data as a form or JSON, and click "Run Test". Each node shows its output inline; a red outline indicates an error.

Can I use custom code in an automation?

Yes. Add a Code by UnifyApps node and write JavaScript, Groovy, Python, or Java directly in the editor. The node returns whatever your script returns, which is available as a data pill to downstream nodes.

How do I troubleshoot a failed run?

Open the automation's Runs tab, locate the failed run, and click it. The canvas shows the step where execution stopped in red. Select that step to see its Input, Output, and Error details, including the HTTP status code and error message.

Step inputs and outputs are recorded only when Settings › Logging › Capture depth is set to Full trace. The default, Run summary, keeps only the run's status, start time and duration, so raise the capture depth before reproducing the failure.

Can I schedule an automation to run on a recurring basis?

Yes. Choose Schedule as the trigger, then set an interval (every N seconds, minutes, hours, days, weeks or months — minimum 15 seconds; the default is every 15 minutes) or a cron expression, with a time zone.

Can I collaborate with team members on an automation?

Yes. Share an automation with teammates from its row menu (Share); they see it once it's shared with them. Use the Versions tab to see who deployed each version and restore an earlier one.