What triggers can start an agent?#
Four ways, and you pick one per agent as its first step. The trigger nodes sit in the Triggers group at the top of the node palette.
| Trigger | Starts the agent when | Typical job |
|---|---|---|
| Schedule | The clock reaches the time you pick: every day, every weekday, every week or every month | Monday pipeline report, daily inbox brief, monthly invoice sweep |
| Webhook | Another app sends an authenticated request to the agent | A form tool, a store or a code push hands off work |
| CRM Trigger | Something happens in your Agent Studio CRM | New lead texted in seconds, missed caller texted back, overdue invoice chased |
| Input | Someone runs it on demand from its page, the API or another agent | A teammate pastes a contract and gets a red-flag summary |
How do I schedule an agent to run automatically?#
Add a Schedule node and pick the cadence in the Runs field: Every day, Every weekday, Every week on the day you choose, or Every month on any day from 1 to 28. Set the time and the inspector converts it for you, for example That's 9:00 AM your time. Power users can type a five-field cron expression straight into Cron schedule.
Put an agent on a schedule
Step 1: Open the agent on the canvas
Pick an agent from your dashboard, or start a fresh one.Open your agentsStep 2: Add the Schedule trigger
Drag Schedule from the Triggers group and connect it to the first working step.Step 3: Choose when it runs
Pick the cadence and time in Runs. Schedules are stored in UTC and the inspector shows your local time beside it.Step 4: Set default fields
In Default fields, name the values each scheduled run reads, such as{"topic": "weekly pipeline"}. A person running it on demand can override them.Step 5: Test it free, then launch
Press Run test to fire one pass right now with your default fields. When the output looks right, save a version and launch so the schedule takes over.
How do I start an agent from a webhook?#
Add a Webhook node as the first step. It starts the agent whenever an authenticated request arrives, and Agent Studio generates the signing secret for you when you launch. Use Default fields to name the body fields you expect, like {"repository": ""}; those names become the agent's published input contract, and the incoming payload fills them. The Source note field is a label for your own reference, such as Stripe payment events.
Developers can point any service that sends webhooks at the agent. For outbound webhooks and signatures, see Webhooks.
Which CRM events can trigger a workflow?#
More than 100, picked in the CRM Trigger node's When field and grouped by area so you find them fast:
- Contacts: Contact created, Contact changed, Tag added, Tag removed, Prospect audit completed.
- Opportunities: Opportunity created, Pipeline stage changed, Opportunity won, lost or reopened, Opportunity stale.
- Appointments: Appointment booked, cancelled or rescheduled, and Appointment reminder due.
- Messages and calls: Customer replied, Missed call, Web chat started, AI replied in a conversation.
- Forms, payments and documents: Form or survey submitted, Invoice paid in full, Invoice overdue, Estimate accepted.
- Tasks and notes, Email marketing, Reviews, Memberships and communities, Social and ads, and Agency round out the list.
Narrow any event with filters: Only with tag, Only in pipeline, Only for stage, Only with status, Only for form and Only on channel. A stage-change trigger filtered to your proposal stage, for example, fires only when a deal reaches proposal.
Can developers set triggers in code?#
Yes. The @suedeai/agents SDK exposes the same triggers as functions, and one agent can list several.
schedule("0 13 * * 1-5") // weekdays at 13:00 UTC
manual() // run on demand
webhook() // start from an inbound request