Skip to content

Connector documentation

Guides for configuring built-in connector types and working with connector instances in Floh.

Topic Document
Creating instances & execution models Creating connectors
Day-to-day CRUD & lifecycle Connector management
Resource sync Resource sync
Outbound SCIM (Floh → IdP) SCIM outbound
Inbound SCIM (Entra → Floh) Entra setup for Floh
Okta directory (Floh → Okta) Okta connector
Microsoft Entra ID (Floh → Entra) Entra ID connector
SMS providers (Twilio, Vonage) SMS providers
Twilio setup (non-technical) Twilio setup guide
Testing connectors Testing

Built-in connector reference

Setup, connection fields, commands, and troubleshooting for registered built-in types:

Type Connector type Guide
Google Workspace google-workspace Google Workspace connector · GCP setup
Slack slack Slack connector
Plane (ITSM peer) plane Plane connector
Jira Software (ITSM peer) jira Jira connector
ServiceNow incident (ITSM peer) servicenow ServiceNow connector
HashiCorp Vault KV v2 vault Vault KV connector
AWS S3 / S3-compatible s3 S3 connector
Okta directory okta Okta connector
Microsoft Entra ID entra-id Entra ID connector · App-registration setup

For other built-in types (authifi, http, scim, etc.), see Creating connectors and the handler under packages/server/src/modules/connectors/handlers/.

Implementing a new built-in type

Handler code lives in packages/server/src/modules/connectors/handlers/. Add a developer guide under docs/connectors/<name>-connector.md and a short pointer README in the handler’s *-support/ folder (see existing Slack, Vault, and S3 layouts).