Trigger blocks

Manual Trigger

Use Manual Trigger when a workflow should be started from the Builders UI, such as refreshing customer data or running an internal report on demand. It accepts manually provided JSON input and returns that payload as the first workflow input, together with run metadata. Use it for testing before exposing an endpoint or schedule.

Cron Trigger

Use Cron Trigger for scheduled workflows: daily reports, periodic external checks or weekly reminders. It accepts a schedule expression and optional timezone or payload settings, then returns schedule metadata and the configured payload. Cron output should normally be normalized with Transform before calling external systems.

Endpoint Trigger

Use Endpoint Trigger when the workflow should behave like an HTTP endpoint or webhook. Configure the HTTP method, sync or async mode, optional JSON Schema validation and file upload support. It accepts request body, query parameters, headers and uploaded files. It returns a request-shaped JSON object that later blocks can read with template expressions. In sync mode, the workflow should finish with a Render Block or response-shaped output so callers receive a predictable status, body and content type.

Web Form Trigger

Use Web Form Trigger when users should submit a public or protected form. Supported fields include text, textarea, radio, checkbox, dropdown, password, file upload, static text, image, separator and columns. It returns submitted field values, file references and form metadata. Required fields should be validated in the form and again in the workflow when the result drives payment, user updates or external writes.

Email and messaging triggers

Email Trigger starts from inbound mail. Messaging triggers cover Slack, Twilio SMS, Signal, Microsoft Teams and WhatsApp Business events. They accept provider webhook or polling data and return normalized message metadata: sender, recipient or channel, text body, attachments and provider IDs. These triggers are visible only when a compatible integration exists for the project owner or team.

Queue and issue triggers

Queue Trigger works with RabbitMQ, ActiveMQ, AWS SQS and AWS SNS. Issue Trigger works with Jira, GitHub Issues and GitLab Issues. Queue output contains the message body, headers or attributes and acknowledgement data when the provider needs it. Issue output contains event type, issue identifiers, title, body, labels, author and raw provider payload for advanced routing.