Skip to main content
A trigger adds a task to a workflow’s task board each time something happens in another app. A new ticket, a form response or a paid invoice becomes a task, filled in from the event, ready for Arro to work through.

​
Where to find it

Open a workflow and choose the Triggers tab. Everyone who can see the workflow sees its triggers. Only the workflow’s owner can add, change, turn off or delete them.

​
Add a trigger

1

Choose Add trigger

On the Triggers tab, choose Add trigger, then pick the app. For an app that isn’t listed, choose Any app: it works with anything that can send a POST.
2

Pick the event

Pick the event that should add a task, such as New issue or Payment failed. One trigger is one event, so add a trigger for each event you want. Zapier, Make, n8n, Jira and HubSpot skip this step: the Zap, scenario or flow on their side decides when it sends.
3

Paste the URL into the app

Copy the URL and paste it into the app, following the steps the setup shows.
4

Send one event

Make the event happen once in that app. The setup waits for it, so what you map is what your app really sends. Any other event the app sends, like a test ping, is skipped.
5

Fill in the fields

Choose which part of the event goes into each field of the task, then choose Turn on.
Give the trigger a name in setup, like New lead from the website. To change it later, open the trigger’s ... menu and choose Rename. Each trigger’s switch turns it on or off. The URL is shown once. Anyone who has it can add tasks, so keep it private. If it leaks or you lost it, open the trigger’s ... menu and choose Get a new URL. The old one stops working right away, so paste the new one into your app too. A trigger you didn’t finish reopens on its URL step, where you can also get a new one.

​
Signing secret

GitHub, Shopify, Stripe, Typeform, Tally and Jira webhooks can sign each event with a secret. On the URL step, paste that secret into Signing secret and choose Save. Each app’s guide shows where its secret is. From then on, the trigger refuses any request that isn’t signed with it. The setup and the trigger’s activity show a refused request and why, once an hour for each reason. An app that keeps a delivery log shows every one there. The field is optional, and a trigger without a secret works the same as before. The secret is never shown again after you save it. To replace or remove it, open the trigger’s ... menu, choose Edit fields, then Back. Each guide shows where the URL goes in that app and how to send its first event.

​
Fill in the task

Your task’s fields are on the left. For each one, pick the part of the event that fills it, type a value every task gets, or leave it empty. Under each field you see what your app’s event gives it. A value that does not fit never stops the task from being added. The task is added without it, and the trigger’s activity says which field was left empty and why.

​
Where tasks go

Choose under Where new tasks go. Tasks in the pick-up list start only while the owner’s computer is on with the Audimate app open, and while Arro is on for the task board. If Arro is off, the setup shows Enable to turn it on. Tasks that start on their own run a snapshot of the workflow, never the working copy, so editing the playbook does not change what runs. Pick one under Runs, or choose Take snapshot right there. Pages the playbook links to are always read as they are now. If someone else becomes the workflow’s owner, new tasks go to the Inbox until they choose the list again. Being handed a workflow never starts work on your computer.

​
Activity

Choose a trigger to see its recent events: when each arrived, and whether it added a task. An event that failed, or that arrived during setup, can be added as a task with Replay. A request refused for its signature shows as Refused, with the reason. It kept nothing to replay, so send it again from the app. While a trigger is off, events it receives are not added, and the sending app keeps its setup. A trigger that fails five events in a row turns itself off, and its owner gets a notification. Fix the cause, then turn it back on with its switch.

​
Limits

A workflow’s triggers share its hourly limit. Past it, they refuse events until the hour is up, and each trigger’s activity shows Over the hourly limit once. Every plan includes triggers. Adding a task uses none of your monthly usage. A task that runs uses it as any task does.

Workflows

The workflow whose task board a trigger fills.

Task boards

Where trigger tasks wait and how they start.

Scheduled tasks

Add work on a schedule instead of on an event.