# Overview

Triggers are the core ways to start SteelEngine workflows

![Triggers Overview](https://docs.steelengine.com/static/blocks/triggers.png)

## Core Triggers

Use the Start block for everything originating from the editor, deploy-to-API, or deploy-to-chat experiences. Other triggers remain available for event-driven workflows:

[Start](/triggers/start)

Unified entry point that supports editor runs, API deployments and chat deployments

[Webhook](/triggers/webhook)

Receive external webhook payloads

[Schedule](/triggers/schedule)

Cron or interval based execution

[RSS Feed](/triggers/rss)

Monitor RSS and Atom feeds for new content

[Framer](/triggers/framer)

Start a workflow from signed Framer native form submissions

[Email Polling Groups](#email-polling-groups)

Monitor team Gmail and Outlook inboxes

## Quick Comparison

| Trigger                  | Start condition                                       |
| ------------------------ | ----------------------------------------------------- |
| **Start**                | Editor runs, deploy-to-API requests, or chat messages |
| **Schedule**             | Timer managed in schedule block                       |
| **Webhook**              | On inbound HTTP request                               |
| **RSS Feed**             | New item published to feed                            |
| **Framer**               | Signed form submission delivered by Framer            |
| **Email Polling Groups** | New email received in team Gmail or Outlook inboxes   |

> The Start block always exposes `input`, `conversationId`, and `files` fields. Add custom fields to the input format for additional structured data.

## Using Triggers

1. Drop the Start block in the start slot (or an alternate trigger like Webhook/Schedule).
2. Configure any required schema or auth.
3. Connect the block to the rest of the workflow.

> Deployments power every trigger. Update the workflow, redeploy, and all trigger entry points pick up the new snapshot. Learn more in [Execution → Deployment Snapshots](/execution).

## Manual Execution Priority

When you click **Run** in the editor, SteelEngine automatically selects which trigger to execute based on the following priority order:

1. **Start Block** (highest priority)
2. **Schedule Triggers**
3. **External Triggers** (webhooks, integrations like Slack, Gmail, Airtable, etc.)

If your workflow has multiple triggers, the highest priority trigger will be executed. For example, if you have both a Start block and a Webhook trigger, clicking Run will execute the Start block.

**External triggers with mock payloads**: When external triggers (webhooks and integrations) are executed manually, SteelEngine automatically generates mock payloads based on the trigger's expected data structure. This ensures downstream blocks can resolve variables correctly during testing.

## Integration Triggers

Many integrations can also start a workflow from their own events. The toolbar's **Triggers** section lists Start, Schedule, and Webhook first, then every integration trigger in alphabetical order.

To add one:

1. Drag the integration from the **Triggers** section onto the canvas, or click it.
2. Pick the event to listen for.
3. Connect the credentials the integration needs.

See [Trigger Mode for Service Blocks](/triggers/webhook#trigger-mode-for-service-blocks) for details.

Slack triggers use a workspace bot installation from the hosted Slack app or a [custom app](/credentials/custom-apps#events-and-channels). Select one or more events from the app's saved bot subscriptions in **Events to match**, or use **All events**. Any selected event can trigger the workflow within the channel and access restrictions. Apply optional channel and message filters. The app has one Events API URL shared by its workflows. Personal Slack user connections are available for actions, not workflow triggers.

The list below groups the integrations that have triggers. Each tool page lists the events it exposes and their output fields under **Triggers**.

* **Development and project management**: [Linear](/tools/linear), [Notion](/tools/notion), [Confluence](/tools/confluence), [Jira](/tools/jira), [GitHub](/tools/github), [Monday](/tools/monday), [Vercel](/tools/vercel), [Azure DevOps](/tools/azure_devops)
* **CRM and sales**: [HubSpot](/tools/hubspot), [Attio](/tools/attio), [Salesforce](/tools/salesforce), [Intercom](/tools/intercom), [Stripe](/tools/stripe)
* **Outreach and email delivery**: [Instantly](/tools/instantly), [Email Bison](/tools/emailbison), [Lemlist](/tools/lemlist), [Resend](/tools/resend), [Sendblue](/tools/sendblue)
* **Recruiting**: [Greenhouse](/tools/greenhouse), [Ashby](/tools/ashby)
* **Meetings and calls**: [Cal Com](/tools/calcom), [Grain](/tools/grain), [Zoom](/tools/zoom), [Calendly](/tools/calendly), [Circleback](/tools/circleback), [Fathom](/tools/fathom), [Gong](/tools/gong), [Fireflies](/tools/fireflies), [Twilio Voice](/tools/twilio_voice)
* **Messaging**: [Microsoft Teams](/tools/microsoft_teams), [Slack](/tools/slack), [Telegram](/tools/telegram), [WhatsApp](/tools/whatsapp)
* **Forms and sites**: [Webflow](/tools/webflow), [Google Forms](/tools/google_forms), [Typeform](/tools/typeform)
* **Email inboxes** (polling): [Gmail](/tools/gmail), [Outlook](/tools/outlook), [IMAP Email](/tools/imap)
* **Google Workspace** (polling): [Google Calendar](/tools/google_calendar)
* **Data**: [Airtable](/tools/airtable)

Polling triggers check the account on a schedule instead of receiving a webhook. SteelEngine disables a polling trigger after 100 consecutive failed polls. The other triggers receive webhooks. Depending on the provider, SteelEngine registers the webhook when you deploy, or the trigger's setup instructions show you where to paste the webhook URL.

## Email Polling Groups

Polling Groups let you monitor multiple team members' Gmail or Outlook inboxes with a single trigger. Requires a Team or Enterprise plan. **Email Polling** appears in Settings only when your deployment enables it with the `NEXT_PUBLIC_CREDENTIAL_SETS_ENABLED` toggle (see [Self-Hosted Configuration](/enterprise#self-hosted-configuration)).

**Creating a Polling Group** (Admin/Owner)

1. Go to **Settings → Email Polling**
2. Click **Create** and choose Gmail or Outlook
3. Enter a name for the group

**Inviting Members**

1. Open your polling group
2. Type each address into the **Enter email addresses** field. You can also drop a CSV or TXT file to add every address it contains
3. Click **Invite**

Invitees receive an email with a link to connect their account. Once connected, their inbox is automatically included in the polling group. Invitees don't need to be members of your SteelEngine organization.

New users can open an active invitation emailed to them and create a SteelEngine account using that same email address, with a password or Google. They return to the invitation to accept it and connect their inbox. Shared invitation links without an email addressee require an existing SteelEngine account.

**Using in a Workflow**

When configuring an email trigger, select your polling group from the credentials dropdown instead of an individual account. The system creates webhooks for each member and routes all emails through your workflow.

## Common Questions

**Can I have multiple triggers on the same workflow?**

Yes, a workflow can have multiple triggers (for example, a Start block and a Webhook trigger). When you click Run in the editor, SteelEngine executes the highest-priority trigger: Start block first, then Schedule, then external triggers like webhooks. Each trigger type can also fire independently when its event occurs.

**How do I secure my webhook endpoint?**

The Generic Webhook trigger authenticates requests by default: Require Authentication is on and an Authentication Token is generated when you add the block. Optionally specify a custom header name. Incoming requests must include the token as a Bearer token in the Authorization header (or in your custom header). Requests without a valid token are rejected with 401.

**What happens when I test an external trigger manually?**

When you click Run on a workflow with an external trigger (webhook, Slack, Gmail, etc.), SteelEngine generates a mock payload based on the trigger's expected data structure. This lets downstream blocks resolve their variable references correctly so you can test the full workflow without waiting for a real event.

**Do triggers use the draft canvas or the deployed version?**

All trigger-based executions (API, chat, schedule, webhook) run against the active deployment snapshot, not your draft canvas. After making changes, you need to redeploy for triggers to pick up the updated workflow version.

**What integrations are available as triggers?**

The Integration Triggers table on this page lists every integration with a trigger and how many event types it exposes, from development tools like GitHub, Linear, and Jira to CRM, email, meeting, and messaging providers. Each integration provides event-specific triggers such as an issue being created or an email arriving, and its tool page documents the events and their output fields.

**How does the Schedule trigger work?**

The Schedule trigger runs your workflow on a timer using cron expressions or interval-based configuration. The schedule is managed within the schedule block settings. Like all triggers, scheduled runs execute the active deployment snapshot, so make sure to redeploy after making workflow changes.
