Overview

Triggers are the core ways to start SteelEngine workflows

Triggers Overview

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:

Quick Comparison

TriggerStart condition
StartEditor runs, deploy-to-API requests, or chat messages
ScheduleTimer managed in schedule block
WebhookOn inbound HTTP request
RSS FeedNew item published to feed
FramerSigned form submission delivered by Framer
Email Polling GroupsNew 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.

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 for details.

Slack triggers use a workspace bot installation from the hosted Slack app or a custom app. 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.

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).

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

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.
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.
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.
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.
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.
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.

On this page