Triggers and schedules
Start a workflow by hand, on a schedule, from a webhook or form, or when a new email or Jira issue arrives.
How a workflow starts is set in the Triggers section of the start node's panel on the canvas. A workflow can have several triggers at once; the canvas sums them up, for example "Manual · 2 schedules · 1 webhook". Schedules, forms, webhooks and app triggers always start the deployed version.
| Trigger | Starts the workflow | Plan |
|---|---|---|
| Manual | When you press Run or ask for a run in chat | Every plan |
| Schedule | At set times | Business and Enterprise |
| Webhook | When another system calls a signed URL | Every plan |
| Form | When someone submits a public form | Every plan |
| App | When a new email arrives in Gmail or Outlook, or a new issue in Jira | Free: 1 trigger, checked at most every 10 minutes. Business: 10, every 2 minutes. Enterprise: 25, every minute |
Creating and viewing webhook, form and app triggers is for workspace admins and team managers.
Manual
Always available. Use Run at the top of the workflow page, or ask for a run in a chat. If the workflow has inputs, the Run workflow panel asks for them and shows a cost estimate and your balance first. You can also add files as run input. For a draft you are still building, use Test run. See Build a workflow.
Schedules
In Triggers, under Schedules, choose Add schedule. Give it a Name such as "Daily report", pick a preset such as Daily at 09:00 or a cron expression, and the timezone. Under Input (optional, JSON) you can pass the same values into every run. Choose Create trigger.
You can add a schedule before the first deploy; it starts running once the workflow is deployed. Read Scheduled agents and workflows for what scheduled runs cost and what to check before you rely on them.
Webhooks
- Under Webhooks, choose Add webhook.
- Enter a name and an optional description, then Create webhook.
- Copy the Webhook URL and the Signing secret. The secret is shown only once.
The calling system sends an X-Webhook-Timestamp header (Unix seconds) and an X-Webhook-Signature header: the base64 HMAC-SHA256 of {timestamp}.{raw body}, keyed with the secret. Requests older than 5 minutes are refused. The JSON body becomes the run's input. The status codes are listed on Schedules and triggers for agents.
Forms
Under Forms, choose Add form. Design the fields, the submit button and the message people see afterwards. You get a Public form link: anyone with it can submit the form, and every submission starts a run with the filled-in fields as input. Use Disable this form to stop accepting submissions. Until the workflow is deployed, the link refuses submissions.
App triggers
Under Apps, choose Add app trigger. On New app trigger:
Choose the event
Under When this happens, pick a new email in Gmail, a new email in Outlook, or a new issue in Jira.
Choose the account
Pick the Connected account, or Connect one.
Narrow it down (optional)
- Gmail: a Gmail label and Extra search terms, such as
from:billing@acme.com. - Outlook: a Folder, search terms, and a Shared mailbox such as
invoices@yourcompany.com. A shared mailbox needs access from your Microsoft admin. - Jira: a Project key and Extra JQL, such as
priority = High.
- Gmail: a Gmail label and Extra search terms, such as
AgentWorks checks for new items on your plan's interval. For mail, the attachments of each new email (up to 10 files, 25 MB each) are passed to the run as files.
Money and runs
- Runs started by a schedule, webhook, form or app trigger are paid from extra usage only, not from the monthly balance.
- Every run of a deployed workflow counts towards your monthly workflow runs, however it started. When runs are used up, scheduled and app-triggered workflows are switched off, and manual runs, webhooks and forms are refused until you buy a run pack or the month turns.
See Plans and billing.
The Triggers page
All triggers of the workspace, for agents and workflows, are on the Triggers page. Find it with the search at the top of the app. Each row shows its type (Webhook, Form or App), and View fire history shows when it fired.