Connector catalog
Pre-built integrations with 40+ services. Each connector exposes a set of operations (and often a set of event triggers) for one external service.
This page is the index. Individual connector pages live alongside this README, they cover:
- The operations and triggers the connector exposes.
- How to authenticate (OAuth scopes, API key permissions).
- Common gotchas specific to the service.
By category
CRM & sales
- Salesforce, Accounts, contacts, leads, opportunities, cases, custom objects
- HubSpot CRM, Contacts, companies, deals, pipelines
- Pipedrive, Pipelines, deals, persons
- Microsoft Dynamics 365
- SAP S/4HANA
Communication & chat
- Slack, Messages, channels, files, users, reactions; events
- Microsoft Teams, Messages, channels, meetings
- Google Chat, Messages, spaces, threads
- Telegram, Bot messages, channels
- Discord, Messages, channels, roles
- Discourse, Topics, posts, users
Email & marketing
- SendGrid, Send email, manage contacts, campaigns
- Mailchimp, Lists, campaigns, subscribers
- Postmark, Transactional email
- HubSpot Marketing, Campaigns, marketing contacts
- Buffer, Schedule social posts
Productivity & docs
- Google Drive, Files, folders, permissions
- Google Sheets, Rows, columns, formulas
- Google Docs, Documents, content
- Microsoft OneDrive / SharePoint
- Microsoft Excel, Workbooks, sheets
- Notion, Databases, pages, blocks
- Airtable, Records, tables, views
- Dropbox, Files, folders
Project management
- Jira, Issues, sprints, boards
- Asana, Tasks, projects
- Trello, Cards, lists, boards
- ClickUp, Tasks, spaces
- Linear, Issues, projects, cycles
- GitHub / GitLab, Repos, issues, PRs, branches, releases
E-commerce & payments
- Stripe, Charges, customers, subscriptions, invoices
- Shopify, Products, orders, customers
- Magento B2B
- Square, Catalogue, transactions
- Plaid, Bank accounts, transactions
Cloud platforms
- AWS, S3, SNS, SQS, Lambda, Athena, Rekognition, Textract, Translate, Transcribe, Secrets Manager
- Azure, Functions, Blob Storage, Service Bus, EventGrid, Logic Apps
- Google Cloud Platform, Storage, Pub/Sub, Cloud Functions, Natural Language, Translation
- Snowflake, Queries, warehouses
Identity & enterprise
- Okta, Users, groups, applications
- Auth0, Users, roles
- OneLogin
- Active Directory / LDAP
Documents & e-sign
- DocuSign, Envelopes, recipients, templates
- PandaDoc
- Adobe Sign
IT service management
- ServiceNow, Incidents, requests, tasks
AI & data
- OpenAI, Completions, embeddings, fine-tuning
- Anthropic, Claude messages, embeddings
- Google Vertex AI
- Pinecone / Weaviate / Chroma / Milvus, Vector databases
Calendar & video
- Google Calendar, Events, invitations
- Microsoft Outlook Calendar
- Zoom, Meetings, recordings
- Vimeo, Videos
- Spotify, Playlists, tracks
Other
- Wikimedia / Wikipedia
- Instagram, Posts, media
- Medium, Articles, publications
- Datto Autotask PSA
- Postman, Collections, environments
Per-connector pages
Each connector has its own page in this folder. Examples:
The Flero repository's docs/connectors/ directory contains the existing per-connector pages, those should be merged into this folder during the docs restructure described in the plan file.
When there's no connector
For services without a Flero connector, use the HTTP Request node. Combined with an API-key credential, you can integrate with any HTTP-based API.
If you build a useful integration that way, consider packaging it as a marketplace plugin so others can reuse it.
Related
Found something out of date? This page lives in the Flero docs content set.