Skip to content

Connector catalog

Flero ships connectors for dozens of services. Each connector is a node that runs one operation against the service's API, and most come with a trigger node too.

This page lists the current catalog, links the setup guides, and explains what every connector has in common.

Connector guides

Connector Auth Triggers Availability
Slack Flero-managed sign-in, your own Slack app, bot token Real-time: New message, Slash command, Button clicked Connector: all. Triggers: limited
HubSpot CRM Flero-managed sign-in, your own app, private-app token Polling Connector: all. Trigger: limited
Microsoft Outlook Flero-managed sign-in, your own Entra app Polling All
Granola API key Real-time and polling All
Databricks Personal access token, OAuth with your own app Polling All
Trello API key Polling Connector: all. Trigger: limited
Salesforce Flero-managed sign-in, your own connected app Polling Limited
Jira Basic (not working, see page) Polling Limited
ServiceNow OAuth with your own app Polling Limited
Shopify Admin API access token, OAuth with your own app Polling Limited
DocuSign OAuth with your own integration key, access token Polling Limited
SAP S/4HANA Access token Polling Limited
Microsoft Dynamics 365 OAuth Polling Limited
Google Cloud Service-account key, Google sign-in Polling Limited
Azure OAuth Polling Limited
AWS API key (not working, see page) Polling Limited

Limited means the node is not in the palette for customer workspaces yet. Workflows that already contain it keep their configuration. Each limited page explains what works today.

Other connectors in the palette

These connectors are available to everyone. They follow the common patterns below and have no separate guide yet.

Area Connectors
Google Workspace Gmail, Google Calendar, Google Chat, Google Docs, Google Drive, Google Sheets, Google Slides (each with polling triggers)
Microsoft 365 Teams, SharePoint, OneDrive, OneNote, Excel
Productivity and data Airtable, Notion, Asana
Developer tools GitHub (with a trigger), Bitbucket, CircleCI, Postman
Identity Okta Users
Workspace management Nexudus

Google Workspace connectors need your own Google OAuth app for now. See OAuth flow.

Many more connectors exist in limited release, including Stripe, Zoom, SendGrid, ClickUp, GitLab, Telegram, WhatsApp Business, Square, Plaid, Pinecone, OpenAI, Mandrill, Vimeo, Spotify and the individual AWS services.

What every connector has in common

Adding one

  1. Drag the connector from the palette's Integrations category.
  2. Pick a credential, or click Sign in with … where offered.
  3. Pick the Resource (where the connector groups its operations) and the Operation.
  4. Fill in the operation's fields. Many fields are dropdowns filled live from the service, such as Slack channels or HubSpot pipelines. Use the refresh button beside a dropdown to reload it.

Output

A connector operation returns one item:

{ "success": true, "statusCode": 200, "data": { }, "operation": "postMessage" }

data is the service's response. Read it downstream with {{ $node["Post to channel"].output.data.ts }}. Some hand-built operations add extra fields, and their guide says so.

Errors and retries

A response outside the 2xx range fails the node. Connectors have no error output port. Use the node's error mode in Node Settings instead:

  • Retry tries again, 3 times by default, with a delay that doubles from 1 second. Every error is retried, including validation errors.
  • Continue lets the workflow carry on past the failure.

When an OAuth service rejects a call with 401, Flero refreshes the token once and retries before failing.

Flero does not throttle connector calls. The service's own rate limits apply, and a 429 fails the node like any other error.

Common errors

Error What to do
401 The token is wrong, expired or revoked. Edit the credential and Reconnect, or paste a new key.
403 The account or app lacks a permission. Check the scopes on the connector's page.
404 A wrong ID, or the record is outside what the credential can see.
429 Rate limited. Use the Retry error mode, or space out the calls.

When there's no connector

Use the HTTP Request node with a Generic / Custom HTTP credential. See API keys & bearer tokens.

Found something out of date? This page lives in the Flero docs content set.