Integrations
Automation integration catalog
Browse the apps FastHook can use as Workflow Triggers and Actions. Open a provider to review its operations, authentication model, permissions, and schema details.
Communication and messaging
Team chat, email, SMS, voice, and bot platforms used for notifications and conversations.
Files and productivity
Spreadsheets, calendars, cloud files, and productivity suites for everyday operational work.
Projects and knowledge
Project tracking, planning, and knowledge tools that keep teams and their work organized.
Developer tools
Source control and engineering platforms for repository, issue, and delivery automation.
Sales, data, and commerce
Customer, database, and ecommerce systems used to move business records through a Workflow.
Payments
Payment and billing providers for reacting to transactions and automating financial operations.
More integrations and utilities
- HTTP — Call external HTTPS APIs from a FastHook Workflow and configure request inputs with optional bearer, API key, or basic authentication.
- ActiveCampaign — Start Workflows from contact, campaign, deal, list, and SMS events, then manage CRM and marketing records through the ActiveCampaign API.
- Webflow — Start Workflows from Webflow site, CMS, form, ecommerce, and comment events, then manage content and commerce through the Data API.
- Klaviyo — Start Workflows from new profiles and events, manage customer profiles and lists, and send behavioral events to Klaviyo.
- Jotform — Start FastHook Workflows from Jotform submissions, retrieve form questions and response data, and map answers into downstream Actions.
- Brevo — Connect Brevo to FastHook to automate contact and list changes, react to email delivery events, and send transactional email messages.
- Zoom — Connect Zoom to FastHook, trigger Workflows from meeting and recording events, schedule meetings, and manage participant registrations.
- Typeform — Connect Typeform to FastHook, start Workflows from form submissions, retrieve response data, and create or update forms through Actions.
- Mailchimp — Connect Mailchimp to FastHook to react to audience changes, add or update subscribers, manage contact tags, and create campaign drafts.
- Google Forms — Start Workflows from new or edited form responses, monitor form changes, and create, update, publish, or read Google Forms.
Universal integrations
Use a Webhook Source to trigger a Workflow from any service that can send HTTP. Use a Destination Step for a reusable HTTP, CLI, or other delivery transport. These are not tied to a provider Action catalog and are useful for internal APIs and unsupported apps.
How to choose a trigger
- Search the Source dialog for the provider.
- Select the event definition that matches the business event.
- Compare instant and polling variants when both exist.
- Connect the account and restrict the Source to the required resources.
- Review the Trigger output sample before mapping Actions.
Provider Sources can expose filters such as spreadsheet, worksheet, Gmail query, Slack channel, GitHub repository and event type, Stripe event type, file path, project, team, or workspace. Available fields depend on the selected definition.
How to choose an Action
- Select the provider and named operation in the Action dialog.
- Choose an authentication mode supported by that Action.
- Select targets with the provider resource picker where available.
- Map content from the Trigger or earlier Steps.
- Review advanced fields only when the provider behavior requires them.
Action manifests define required permissions, input and output schemas, remote resource dependencies, and rate limits. The dashboard uses these manifests to render the editor and validate saved configuration.
Every provider page lists the current manifest authentication type, base Trigger scopes, operation-specific Action access requirements, auth modes, and rate limits. Use Authentication and permissions when consent succeeds but an account or resource is still unavailable.
Trigger and Action do not need to use the same account
A Workflow can listen in one account and act in another—for example, receive a GitHub event from one organization and create a Linear issue in another workspace. Confirm the FastHook team is allowed to use both accounts and label them clearly.
Integration availability
Provider APIs and FastHook manifests evolve. Treat the provider and operation lists shown in the current dashboard as authoritative when they differ from a static page. Report a mismatch so the documentation can be regenerated from the catalogs.
Next, configure Connected accounts, choose a Trigger, and add an Action.