Agent triggers - Gumloop

Agents can run autonomously without manual interaction. Set up scheduled triggers to run on a recurring or one-time basis, app triggers to fire when something happens in an external service, or a webhook trigger to fire when another app sends data to a unique URL.

All triggers are managed from the Triggers section of your agent’s configuration page. Click Add trigger to create a new one.

Trigger type selector showing Scheduled Trigger and App Trigger options

Need to monitor multiple services, apply custom logic, or watch an app without a pre-built trigger? Use Create With AI to build custom triggers in natural language.

Scheduled triggers

Schedule your agent to run automatically on a recurring schedule or as a one-time trigger. When a trigger fires, the agent receives a prompt you configure and processes it exactly as if you had typed it in the chat.

Setting up a scheduled trigger

Go to your agent’s configuration page, find the Triggers section, and click Add trigger. Choose Scheduled Trigger as the type, then fill in three fields:

Name: A short label (e.g., “Daily Ticket Summary”)
Schedule: When the trigger should run (recurring cron or one-time)
Prompt: The message your agent receives when the trigger fires

Click Create and the trigger is immediately active.

Recurring
One-time

Runs on a cron schedule until you pause or delete it. You don’t need to know cron syntax: describe your schedule in plain language and the AI generates the expression.

Create a Scheduled Trigger dialog showing the Recurring tab with name, AI-powered schedule field, cron expression, and prompt

Minimum interval is 1 minute. Timezones default to your browser’s timezone.

Once created, triggers appear in the Triggers section. Click to edit, or use the three-dot menu to activate, deactivate, or delete.

Triggers section showing a created Tickets Summary trigger that runs every 30 minutes

Writing good trigger prompts

The prompt is what your agent receives when the trigger fires. Be specific:

Good	Bad
”Give me a summary of all the Zendesk tickets created in the last two days."	"Do the usual thing."
"Check my Gmail for unread client emails, summarize them, and post to #client-updates in Slack."	"Check emails.”

If your agent has a relevant skill for the task, reference it in the prompt. The agent will load the skill and follow its instructions for consistent results.

Self-Scheduling

Your agent can create and manage its own triggers during a conversation. Just tell it what you need:

What you say	What happens
”Remind me to check emails every weekday at 9 AM”	Agent creates a recurring scheduled trigger
”In 30 minutes, check if the deployment succeeded”	Agent creates a one-time delayed trigger
”Show me my active schedules”	Agent lists all its triggers
”Pause the daily email check”	Agent deactivates the trigger without deleting it

Agents can only manage their own schedules, not those of other agents.

Webhook triggers

A webhook trigger gives your agent its own URL. Any service that can send an HTTP POST — Stripe, GitHub, a CI job, an internal script — runs the agent by calling it. Unlike app triggers, nothing needs a pre-built integration and Gumloop doesn’t poll anything: the other system calls you.

Setting up a webhook trigger

Add the trigger

On your agent’s configuration page, find the Triggers section, click Add trigger, and choose Webhook.

Trigger menu showing Create With AI, App Trigger, Webhook, Scheduled Trigger, and One-Time Trigger options

Describe what the agent should do

Fill in the trigger and decide how the payload reaches your agent:

Field	Description
Trigger name	A short label (e.g., “Incoming Event”) shown in the Triggers list
Prompt	The message your agent receives when the trigger fires. Drag or click the Raw JSON badge to drop the request body into the prompt.
Send raw JSON instead of a prompt	Sends the payload on its own, with no prompt around it. Use it when the agent’s instructions already explain what to do with the data.

Webhook trigger dialog with Trigger name, a prompt containing the Raw JSON badge, and the Send raw JSON instead of a prompt toggle

A prompt is required unless Send raw JSON instead of a prompt is on.

Copy the URL

Click Create trigger. Gumloop generates a unique URL plus a ready-to-run curl example. Paste the URL into whatever app or script should start the agent.

Trigger created screen showing the webhook URL, a copy button, and a Try it yourself curl example

Need the URL again later? Click the trigger in the Triggers section — the webhook URL is on its detail panel.

Calling the webhook

Send a POST request to the URL. No API key or header is required — the URL itself is the credential.

curl -X POST \
  'https://api.gumloop.com/trigger_incoming_webhook/<trigger_id>/<secret>' \
  -H 'Content-Type: application/json' \
  -d '{"customer": {"email": "ada@example.com"}}'

Gumloop replies 200 with {"success": true} as soon as the request is accepted, then runs the agent in the background — it does not wait for the agent to finish, and the response never contains the agent’s answer. Have the agent report back through a tool (Slack, email, a database write) instead. Payload handling:

JSON is parsed as JSON, even if the sender omits the Content-Type: application/json header.
Form-encoded bodies are turned into key/value pairs.
Anything else is passed through as raw text.

Anyone with the URL can run your agent, so treat it like a password and don’t share it publicly. To retire a URL, delete the trigger — a new trigger always gets a fresh URL.

Every rejected call returns the same 404 not_found, whether the trigger doesn’t exist, is deactivated, or the URL’s secret is wrong. That’s deliberate: a caller holding a bad URL learns nothing about your agents.

Rate limit: each webhook trigger accepts up to 100 requests per minute. The limit is counted per trigger, no matter who sends the request or from which IP, and every request counts toward it, including rejected ones. Requests over the limit get a 429 rate_limited response with a Retry-After header giving the seconds to wait, and the agent does not run for them. If a sender can burst past 100 events a minute, batch or space out its calls, or retry after the Retry-After delay.

Letting your agent manage webhooks

You don’t have to build the trigger by hand. Ask the agent in chat — “give me a webhook I can call from our deploy script” — and it creates one, then tells you to copy the URL from the trigger’s detail panel (the agent never sees the URL itself).

What you say	What happens
”Create a webhook trigger for incoming Stripe events”	Agent creates a webhook trigger, pending your approval
”Show me my webhook triggers”	Agent lists the webhook triggers you created on this agent
”Change the prompt on the Stripe webhook”	Agent updates the trigger’s name, prompt, or raw-JSON setting
”Pause the deploy webhook”	Agent deactivates the trigger without deleting it

Creating, editing, deleting, disabling, and enabling all require your approval before they take effect, and an agent only sees the webhook triggers you created — not ones your teammates added.

Agent-managed triggers require AI Managed to be on in the Triggers header. Turn it off and only you can create or change triggers.

App triggers

App triggers fire your agent when something happens in an external service. Instead of checking manually, your agent reacts automatically to new emails, messages, database changes, and more. When a trigger fires, the event data (e.g., the email body, the Slack message) is injected into a prompt template you write. The agent processes it as if you had typed it in the chat.

Supported integrations

Gmail

New email in a label

Slack

New channel message

Slack reaction

Emoji reaction on a message

Microsoft Teams

New channel message

Google Drive

New file in a folder

Google Sheets

New or updated row

Google Calendar

Upcoming event

Notion

New or updated page

Airtable

New or updated record

Zendesk

New ticket or comment

Salesforce

New or updated record in any object

Linear

New or updated issue

Jira

New issue created

Monday.com

Item, subitem, update, or column change on a board

Parallel Web Monitor

Web changes matching a query

Also supported: Outlook, Outlook Calendar, Google Forms, Typeform, HubSpot, incident.io, and Jira. Some integrations (Gmail, Slack, Slack Reaction, Teams, Drive, Forms, Typeform, Zendesk, Monday.com, Parallel Web Monitor) are real-time and fire within seconds. Others (Sheets, Calendar, Notion, Airtable, HubSpot, incident.io, Salesforce, Linear, Jira) use polling and check for changes approximately every 60 seconds.

Setting up an app trigger

Go to your agent’s configuration page, find the Triggers section, and click Add trigger. Choose App Trigger as the type. Then follow three steps:

Select a trigger

Choose which integration event should fire your agent.

App Trigger picker with a search box and integrations including Google Drive Folder, Google Sheets, Google Calendar Event, Gmail, Outlook, Slack Message, Slack Reaction, Teams Message, Notion Database, Airtable, HubSpot List, Salesforce Record, Zendesk Ticket, Linear Issue, Jira Issue, Outlook Calendar Event, Typeform Submission, Monday.com Board, Google Form Responses, incident.io Incidents, and Parallel Web Monitor

Configure the integration

Connect the account your trigger should use and set its parameters. For example, with Gmail you can choose which label to monitor, whether to mark emails as read, and whether to read HTML content.

Gmail trigger setup with credential selection, label filter, and options for Mark as Read and Read as HTML

Your agent uses the credentials of the person who created the trigger. Make sure you’ve connected the required app on your Connectors page before setting up the trigger.

Write a prompt template

Define what your agent should do when the trigger fires. Use template variables (shown as badges) to inject event data into your prompt.

Prompt template editor showing trigger name and a prompt with template variables like Email Body, Attached File Name, and more

Template variables are specific to each integration. For Gmail, you get variables like Email Body, Subject, Sender, and Attached File Name. For Slack, you get Message, Sender Name, Channel Name, etc.

Prompt templates

When an app trigger fires, the event data is injected into your prompt template before the agent receives it. How it works:

You write a prompt template with placeholder variables (shown as badges in the UI)
When the trigger fires, each variable is replaced with the actual event data
The agent receives the fully resolved prompt and acts on it

Example: Your template:

New email from {Sender}: Subject: {Subject}
{Email Body}
Please categorize this email and draft a response if it's from a client.

When fired, your agent sees:

New email from john@acme.com: Subject: Q1 Budget Review
Hi, can we schedule a meeting to discuss the Q1 budget numbers?
Please categorize this email and draft a response if it's from a client.

You can also toggle Pass Raw Data to send the entire event payload as JSON instead of using template variables. This is useful when you want the agent to decide what’s relevant.

Managing active triggers

All your triggers (scheduled, app, and webhook) appear in the Triggers section of your agent’s configuration. Owners can edit, deactivate, or delete any trigger. Users can always view, deactivate, and delete their own triggers; they can create, edit, and activate their own only when Create triggers is Allow. See Who Can Manage Triggers?. Deactivating every trigger is the supported way to switch an agent off: the agent stops running on its own, but its configuration, connectors, and triggers stay intact and you can re-enable them at any time. Do not use is_active: false on the agents API or gumloop agents update --inactive for this — that retires the agent instead of pausing it.

Triggers tab of an agent listing triggers with a three-dot menu open on Edit, Deactivate, and Delete

Integration details

Gmail

Fires when: A new email arrives in the specified label. (Real-time)Configuration: Choose your Gmail credential, select a label to monitor (e.g., INBOX, a custom label), and optionally enable “Mark as Read” and “Read as HTML”.Available variables: Email Body, Subject, Sender, Attached File Name, Date, Message ID, Thread ID

Due to Google API limitations, only one Gmail account can be monitored per credential. For multiple accounts, create separate triggers with different credentials.

Slack

Fires when: A new message is posted in the specified channel. (Real-time)Configuration: Choose your Slack credential and select the channel to monitor. “Ignore Bot Messages” is enabled by default. You can also optionally ignore thread replies.Available variables: Message, Sender Name, Channel Name, Channel ID, Date, Thread ID, Attachment Names

”Ignore Bot Messages” is on by default to prevent infinite loops if your agent posts back to the same channel. We recommend keeping it enabled unless you specifically need to process bot messages.

Slack reaction

Fires when: Someone reacts to a message with an emoji in the specified channel. (Real-time)Configuration: Choose your Slack credential and select the channel to watch. Optionally filter by specific emoji (e.g., white_check_mark, thumbsup). Leave the emoji filter empty to trigger on any reaction. “Ignore Reactions From Bots” is enabled by default. You can also include or exclude reactions on thread replies, and optionally read the full thread for additional context.Available variables: Message, Emoji, Reaction Count, Reacted By, Message Sender, Attachment Names, Thread ID, Thread Link, Channel Name, Channel ID, Date

”Ignore Reactions From Bots” is on by default. Reactions from Gumloop itself are always ignored regardless of this setting, preventing infinite loops if your agent reacts to messages in the same channel.

Microsoft Teams

Fires when: A new message is posted in the specified Teams channel. (Real-time)Configuration: Choose your Teams credential, select the team and channel. Optionally ignore bot messages and thread replies.Available variables: Message, Sender Name, Channel Name, Channel ID, Date, Subject

Teams triggers only work with Microsoft 365 work or school accounts. Personal Microsoft accounts are not supported.

Want your team to chat with an agent inside a Teams channel instead? See Using Agents in Microsoft Teams.

Google Drive

Fires when: A new file is uploaded to the specified folder. (Real-time)Configuration: Choose your Google Drive credential and select the folder to watch.Available variables: File Name, File ID, File Type, Modified Date

Google Sheets

Fires when: A new row is added or an existing row is updated, depending on your trigger mode. (Polling, ~60s)Configuration: Choose your Google Sheets credential, select the spreadsheet and worksheet. Pick a trigger mode: “Create Row” (new rows only) or “Create or Update Row” (new and modified rows).Available variables: All column values from the row that triggered the event

Google Calendar

Fires when: An event is about to start, an event is about to end, or a new event is created in the future, depending on the trigger mode. (Polling, ~60s)Configuration: Choose your Google Calendar credential, select the calendar, and set how many minutes before the event the trigger should fire (default: 15 minutes).Available variables: Event Title, Start Time, End Time, Attendees, Description, Location

Outlook

Fires when: A new email arrives in your Outlook inbox or a folder you select.Configuration: Choose your Outlook credential and select the inbox or folder to monitor.Available variables: Email Body, Subject, Sender, Attached File Name, Date, Message ID, Thread ID

Outlook Calendar Event

Fires when: An event is about to start, an event is about to end, or a new event is created in the future, depending on the trigger mode.Configuration: Choose your Outlook Calendar credential, select the calendar, and set how far ahead of the event the trigger should fire.Available variables: Event Title, Start Time, End Time, Attendees, Description, Location

Notion

Fires when: A new page is created or an existing page is updated in the specified database. (Polling, ~60s)Configuration: Choose your Notion credential and select the database to monitor.Available variables: All database property values from the page that triggered the event

Airtable

Fires when: A new record is created or an existing record is updated in the specified table. (Polling, ~60s)Configuration: Choose your Airtable credential, select the base, table, and optionally a view. Requires a “Last Modified Timestamp” field in your table.Available variables: All field values from the record that triggered the event

Zendesk

Fires when: Depending on your trigger mode: new ticket created, new comment added, ticket status changed, or ticket enters a view. (Real-time)Configuration: Choose your Zendesk credential and select a trigger mode. Optionally filter by ticket type, priority, or status.Available variables: Ticket ID, URL, Subject, Description, Status, Priority, Type, Requester Email, Assignee Email, Comments

Google Forms

Fires when: A new form response is submitted. (Real-time)Configuration: Choose your Google credential and select the Google Form to monitor.Available variables: All submitted form field values

Typeform

Fires when: A new form submission is received. (Real-time)Configuration: Choose your Typeform credential and select the form to monitor.Available variables: All submitted form field values

HubSpot

Fires when: New records appear in a specified HubSpot list. (Polling, ~60s)Configuration: Choose your HubSpot credential, select the list to monitor, and configure the object type.Available variables: All property values from the records that triggered the event

incident.io

Fires when: A new incident is detected. (Polling, ~60s)Configuration: Choose your incident.io credential. Optionally filter by severity (Minor, Major, Critical) and mode (Standard, Retrospective, Tutorial, Test).Available variables: Incident ID, Name, Status, Severity, Timestamps, Summary, Permalink, Slack Channel ID

Salesforce

Fires when: A new record is created or an existing record is updated in the selected Salesforce object, depending on the trigger mode. (Polling, ~60s)Configuration: Choose your Salesforce credential, select the object to monitor (e.g., Lead, Contact, Opportunity, Account, Case, or any custom object), and choose a Trigger Mode:

New Record: Fires when a new record is created
Updated Record: Fires when an existing record is modified (newly created records are automatically excluded)

Available variables: All fields from the selected Salesforce object (e.g., First Name, Last Name, Email, Company, etc.). The exact fields depend on the object type.

The trigger uses a compound cursor based on the relevant timestamp field (CreatedDate or LastModifiedDate) and record Id to avoid duplicates. It fetches up to 5 records per poll. In Updated Record mode, each modification to a record triggers the agent again.

Linear

Fires when: A new issue is created or an existing issue is updated in the selected Linear team, depending on the trigger mode. (Polling, ~60s)Configuration: Choose your Linear credential, select the Team to monitor (required), and choose a Trigger Mode:

New Issue: Fires when a new issue is created
Updated Issue: Fires when an existing issue is modified (newly created issues are automatically excluded)

Optionally add Filters to narrow which issues fire the trigger:

Status: Filter by issue status (e.g., In Progress, Done, Backlog)
Project: Filter by Linear project
Priority: Filter by priority level (e.g., Urgent, High, Medium, Low)
Labels: Filter by issue labels (matches issues with at least one of the selected labels)
Assignee: Filter by the team member assigned to the issue

Available variables: Description, Identifier (e.g., “ENG-123”), Title, URL, Assignee, Status, Project, Labels

The trigger fetches up to 5 issues per poll. In Updated Issue mode, each modification to an issue triggers the agent again. A Team must be selected — it is a required parameter.

Jira

Fires when: A new issue is created in the selected Jira project. (Polling, ~60s)Configuration: Choose your Jira credential, select the Resource (your Jira instance), the Project to monitor, and optionally apply filters to narrow which issues fire the trigger.Filter options:

Standard Filters: Filter by Status, Priority, Labels, Issue Type, Assignee, and Custom Fields
JQL: Write a custom Jira Query Language expression for advanced filtering
Saved Filter: Use an existing filter saved in your Jira instance

Available variables: Issue ID, Key, Summary, and other issue fields based on the Information to Read selection

The trigger fetches up to 5 new issues per poll. Uses a compound cursor based on the issue’s created timestamp and issue key to avoid duplicates. You must connect your Jira account on the Connectors page before setting up the trigger.

Monday.com

Fires when: Something changes on a Monday.com board — an item, subitem, update, or column event, depending on the Trigger Mode you pick. (Real-time via webhook)Configuration: Choose your Monday.com credential, select the Workspace and Board to watch, then pick a Trigger Mode. Some modes ask for one more field:

Trigger Mode	Extra field
Specific Column Changed	Column — the column to watch
Status Changed To	Status Column, plus an optional Status Value. Leave the value empty to fire on any change to that column.
Item Moved To Group	Group — the destination group

All 18 modes: Item Created, Item Name Changed, Any Column Changed, Specific Column Changed, Status Changed To, Item Moved To Group, Item Moved To Any Group, Item Deleted, Item Restored, Update Posted, Update Edited, Update Deleted, Column Created, Subitem Created, Subitem Name Changed, Any Subitem Column Changed, Subitem Deleted, and Update Posted On Subitem.Available variables: One variable per column on the selected board, named after the column title, plus the board’s item name column (Item, Task, or whatever your board calls its items). Values come from the item behind the event.

Modes where the item no longer exists — Item Deleted, Subitem Deleted, and Column Created — still fire, but the column variables come through empty. Use Pass Raw Data if you need the raw event payload for those.

Subitem events are watched from the parent board you select, and their column values are read from the subitems board, so the variables you get are the subitem’s own columns matched by title.

Monday.com triggers create a webhook on the board, so your connected account needs permission to manage webhooks on it. If you connected Monday.com before this trigger shipped, reconnect it on the Connectors page to grant the webhook permission, otherwise the trigger fails to save.

Parallel Web Monitor

Fires when: Relevant changes are detected on the web matching your natural-language query. (Real-time via webhook)Configuration: No credentials required — works out of the box. Write a Query describing what you want to monitor and set the Frequency for how often to check (hourly, daily, or weekly).Unlike other triggers that watch a specific service, the Parallel Web Monitor uses AI to scan the entire web for material changes matching your query. This makes it ideal for open-ended monitoring like tracking competitors, news, or market changes.Query examples:

“OpenAI product announcements and API pricing changes”
“Acme Corp product launches, pricing changes, and new partnerships”
“YC Startups that have raised Series A funding”
“SEC rulings on cryptocurrency ETF applications”
“New job postings for VP of Engineering at FAANG companies”

Available variables: Event Output, Event Date, Source URLs

Be specific in your query. “AI news” is too broad — “Anthropic and OpenAI model release announcements” will produce much more relevant results.

Choosing the model a trigger uses

Every trigger has a Model field. By default it is set to Use agent model, so the run uses whatever model the agent is configured with. Pick a different model when a specific trigger needs something faster or stronger than the agent’s day-to-day model — for example, keeping an agent on its normal model for chat while a weekly report trigger runs on the smartest one.

Trigger editor showing the Model field open with Use agent model selected, plus Auto, Recommended, Smartest, and per-provider options

Open the Model dropdown while creating or editing a trigger and choose one of:

Option	What it does
Use agent model	Inherits the agent’s selected model. If you later change the agent’s model, this trigger follows along.
Auto, Recommended, Smartest	The same presets the agent’s own model picker offers, so the trigger tracks whichever model currently sits behind that preset.
A specific model	Pinned to that exact model, grouped by provider in the dropdown.

The list shows exactly the models your agent could be set to, so anything your organization has restricted does not appear. If a model you pinned later becomes unavailable — it’s retired, or an admin removes it from the allowed list — the trigger quietly falls back to the agent’s model instead of failing. The Model field is available on scheduled, webhook, app, and MCP triggers, and applies to every run that trigger starts, including runs you fire manually from the Triggers section.

Model choice affects cost. A trigger pinned to a heavier model spends more credits per run than the same trigger on the agent’s default. See Credits for how model usage is billed.

Good to know

File and attachment handling

When a trigger passes files or attachments to your agent, the agent automatically receives and can process them. This includes:

Email attachments from Gmail triggers (PDFs, spreadsheets, images, etc.)
Slack file attachments from Slack message triggers
Google Drive files from Drive triggers (the actual file content, not just the metadata)
Teams attachments from Microsoft Teams message triggers

Your agent can read text-based files (PDFs, CSVs, DOCX, etc.), parse images using vision capabilities, and use file contents as context for its response. No additional configuration is needed.

Credentials

Triggers use the credentials of the person who created the trigger, not whoever is chatting with the agent. Make sure you’ve connected the required app on your Connectors page before setting up a trigger. For team agents, if team credentials are configured, those can be used instead of personal credentials.

Auto-disable on failure

All triggers (scheduled, app, and webhook) automatically deactivate after 3 consecutive failed runs. Common causes include expired credentials, deleted resources (channels, folders, databases), or permission changes. When this happens, the trigger owner receives a notification through email, Slack DM, and in-app. The notification links straight to the most recent failed run so you can see what went wrong. You can dismiss it once you’ve handled it. To fix: resolve the underlying issue, then re-enable the trigger from the Triggers section. Re-enabling resets the failure count, so a trigger won’t be immediately disabled again by earlier failures — only failures that happen after you re-enable it count toward the next auto-disable. For a walkthrough of every reason a trigger turns off and how to fix each one, see Why Did My Trigger Turn Off?.

Overlapping runs

If a previous trigger execution is still running when the next one fires, the new execution is skipped. This prevents duplicate work and ensures your agent finishes one task before starting the next.

Credits

Each trigger execution costs credits based on model and tool usage, the same as a normal chat message. One-time scheduled triggers are automatically deleted after execution (whether they succeed or fail).

FAQ

Can I change a recurring trigger to one-time (or vice versa)?

No. Delete the existing trigger and create a new one with the desired type.

What model does the agent use for triggered runs?

The agent’s own model, unless you set the trigger’s Model field to something else. See Choosing the Model a Trigger Uses.

Are triggered runs visible in history?

Yes. They appear in the agent’s run history as triggered executions.

Can my agent handle file attachments from triggers?

Yes. When a trigger includes files (email attachments, Slack files, Google Drive uploads), the agent automatically receives them and can read text-based files, parse images, and use the content in its response.

Why is there a delay with some triggers?

Some integrations use polling instead of real-time webhooks. Polling-based triggers (Google Sheets, Notion, Airtable, Google Calendar, HubSpot, incident.io, Jira) check for changes approximately every 60 seconds. Real-time triggers (Gmail, Slack, Slack Reaction, Teams, Google Drive, Zendesk, Google Forms, Typeform, Monday.com, Parallel Web Monitor) fire within seconds.

Can one agent have multiple triggers?

Yes. You can add as many scheduled, app, and webhook triggers as you need to a single agent. Each trigger operates independently.

Can my agent create its own app triggers?

Yes! Agents can create and manage their own scheduled triggers and custom AI triggers during conversations. Just describe what you want to monitor and the agent builds it. See Create Triggers With AI for details. Pre-built integration triggers must still be set up from the agent’s configuration page.

Create triggers with AI

Build custom multi-service triggers in natural language

Agents

Learn about building and configuring agents

Agent skills

Teach your agent reusable processes

​Scheduled triggers

​Setting up a scheduled trigger

​Writing good trigger prompts

​Self-Scheduling

​Webhook triggers

​Setting up a webhook trigger

​Calling the webhook

​Letting your agent manage webhooks

​App triggers

​Supported integrations

Gmail

Slack

Slack reaction

Microsoft Teams

Google Drive

Google Sheets

Google Calendar

Notion

Airtable

Zendesk

Salesforce

Linear

Jira

Monday.com

Parallel Web Monitor

​Setting up an app trigger

​Prompt templates

​Managing active triggers

​Integration details

​Choosing the model a trigger uses

​Good to know

​File and attachment handling

​Credentials

​Auto-disable on failure

​Overlapping runs

​Credits

​FAQ

​Related documentation

Create triggers with AI

Agents

Agent skills

Scheduled triggers

Setting up a scheduled trigger

Writing good trigger prompts

Self-Scheduling

Webhook triggers

Setting up a webhook trigger

Calling the webhook

Letting your agent manage webhooks

App triggers

Supported integrations

Setting up an app trigger

Prompt templates

Managing active triggers

Integration details

Choosing the model a trigger uses

Good to know

File and attachment handling

Credentials

Auto-disable on failure

Overlapping runs

Credits

FAQ

Related documentation