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.

23 providers6 groupsSchema-driven operationsProvider authentication documented

Communication and messaging

Team chat, email, SMS, voice, and bot platforms used for notifications and conversations.

Slack
Start Workflows from Slack events and automate messages, reactions, channels, pins, and member operations.
Gmail
Start from received, sent, labeled, searched, or attachment email events and automate common message operations.
Discord
React to Discord gateway events and automate messages, threads, reactions, moderation, roles, and scheduled events.
Twilio
Start from Twilio Event Streams and automate SMS, MMS, WhatsApp, voice calls, and custom API requests.
Telegram Bot
Start from Telegram Bot API updates and send messages through a customer-owned bot.

Files and productivity

Spreadsheets, calendars, cloud files, and productivity suites for everyday operational work.

Google Sheets
Trigger from spreadsheet changes and create spreadsheets, add worksheets, or write and clear ranges.
Google Drive
React to files, folders, comments, spreadsheets, presentations, shared drives, and access proposals, then manage Drive content.
Google Calendar
Trigger from calendar and event lifecycle changes, scheduled start times, or upcoming-event alerts and manage events.
Dropbox
Start from Dropbox file-system changes and automate uploads, folders, moves, copies, deletion, and sharing.
Microsoft 365
Automate Outlook, Calendar, Contacts, Excel, Teams, OneDrive, and custom Microsoft Graph operations.
Microsoft OneDrive
Automate OneDrive file and folder operations through Microsoft Graph; Trigger availability is reported from the current manifest.

Projects and knowledge

Project tracking, planning, and knowledge tools that keep teams and their work organized.

Notion
React to pages, data sources, databases, comments, files, and views and automate Notion content.
Linear
React to Linear workspace events and create or update issues, comments, and projects through GraphQL.
Jira
Start from Jira issue, comment, sprint, version, and property events and automate issue operations.
Asana
Start from signed Asana project events and create, update, complete, organize, or comment on tasks.
Trello
Start from Trello board and card activity and automate cards, lists, labels, members, and comments.

Developer tools

Source control and engineering platforms for repository, issue, and delivery automation.

GitHub
Start from the GitHub webhook catalog and automate repositories, issues, pull requests, and Actions workflows.
GitLab
Trigger from GitLab projects and groups and automate issues, merge requests, comments, and pipelines.

Sales, data, and commerce

Customer, database, and ecommerce systems used to move business records through a Workflow.

HubSpot
React to CRM object and conversation changes and automate contacts, companies, and deals.
Airtable
Start from Airtable record, field, table, and webhook changes and automate records in selected bases.
Shopify
Start from Shopify webhook topics and automate products, orders, and customers through Admin GraphQL.

Payments

Payment and billing providers for reacting to transactions and automating financial operations.

Stripe
Start from the Stripe event catalog and automate customers, payment links, and refunds.
PayPal
Start from PayPal commerce and dispute events and automate orders, captures, payments, and refunds.

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

  1. Search the Source dialog for the provider.
  2. Select the event definition that matches the business event.
  3. Compare instant and polling variants when both exist.
  4. Connect the account and restrict the Source to the required resources.
  5. 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

  1. Select the provider and named operation in the Action dialog.
  2. Choose an authentication mode supported by that Action.
  3. Select targets with the provider resource picker where available.
  4. Map content from the Trigger or earlier Steps.
  5. 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.