Triggers

A Trigger is the event that starts a Workflow. FastHook implements a Workflow trigger with an existing Source, so you configure the provider event once and then select that Source in the Workflow builder.

Trigger families

Provider triggers

Provider triggers listen for a defined activity in an app. Depending on provider capabilities, delivery may be instant, polling-based, or backed by a notification channel with a polling safety path.

Examples include new or changed Google Workspace data, Slack messages and reactions, GitHub repository events, Stripe events, Shopify topics, CRM changes, file events, and issue-tracker activity.

Webhook triggers

A Webhook Source gives any HTTP-capable service a dedicated FastHook URL. Use it for your own application, an unsupported provider, or an event contract you control.

Webhook Sources also expose the lower-level request inspection, verification, response, proxy, and replay capabilities documented under Sources.

Create a trigger from Workflow

1. Select New Workflow.
2. Choose a Source already configured for the event you need.
3. If none exists, use the create-Source option in the same dialog.
4. Select the provider and event definition.
5. Connect an account or enter the credential requested by the provider.
6. Configure event-specific fields such as spreadsheet, channel, repository, event type, or filter.

Instant and polling triggers

An instant trigger receives a provider callback or notification as the event occurs. A polling trigger checks the provider periodically and emits events for newly discovered changes. The provider catalog controls which delivery modes are available for each event definition.

Do not assume two similarly named trigger definitions have the same latency or credential requirements. Choose the delivery mode shown in the Source dialog.

Trigger output

Each trigger definition publishes an output schema and sample when available. The Workflow builder uses that contract to populate the data picker before a real run exists. After a run, the latest trigger preview can provide more representative fields and values.

Operational checks

• Confirm the connected account still has access to the selected workspace, repository, file, calendar, or record collection.
• Verify event filters are not narrower than intended.
• For webhooks, confirm the provider is sending to the current Source URL and passing signature or authentication checks.
• For polling, allow for the configured polling interval before treating an event as missing.
• Inspect Activity and Source run history before changing the Workflow graph.

Next, add an Action and map the trigger data into its fields.