The integration layer includes enterprise connector definitions, event triggers, webhooks, and MCP interfaces. Explore the actions, authentication, and setup work behind each connection.
13 definitions in the source catalog. A listed system is not a verified live connection. Workspace credentials, provider requirements, supported API versions, and end-to-end testing determine availability.
Search by system or action. Open a definition to inspect the connection requirements and the validation work it needs.
13 definitions · Connections require setup and verification.
Authentication OAuth 2.0
An application registration, consent, and the required Microsoft Graph permissions.
Email and calendar records
Review the requested mail, calendar, and file scopes with your workspace administrator.
Authentication OAuth 2.0
An OAuth application, consent configuration, and access to the relevant Google services.
Email records
The definition includes mail, Drive, calendar, and document scopes. Select the minimum access for your pilot.
Authentication OAuth 2.0
Microsoft application consent plus permitted team and channel identifiers.
Message records
Confirm channel access and destination ownership before enabling outbound messages.
Authentication OAuth 2.0
A Slack application, permitted scopes, and access to the selected workspace and channels.
Message records
Validate the current API endpoints and scopes, including file upload and message history access.
Authentication OAuth 2.0
A permitted Zoom application and access to the relevant host accounts.
Meeting records
Meeting and account permissions need to be tested against the connected account.
Authentication Bearer token
A WhatsApp Business account, phone-number configuration, and a permitted access token.
No incremental sync defined
Provider message templates, consent requirements, and delivery rules apply to customer communications.
Authentication Daraja OAuth
Daraja credentials, shortcode and passkey configuration, callback URLs, and sandbox testing.
Transaction adapter definition
The source definition uses Safaricom’s sandbox. Production approval and transaction verification are separate rollout steps.
Authentication API key
Provider-approved credentials, taxpayer configuration, and validation against the required invoice schema.
Invoice adapter definition
This is a connector definition, not a claim of KRA certification or verified production tax compliance.
Authentication OAuth 2.0
Replace the example endpoints with your banking provider’s contract and define the approval policy.
Transaction adapter template
The source uses example.com endpoints. This reference adapter requires bank-specific implementation and testing.
Authentication OAuth 2.0
An authorized application with repository and organization access appropriate to your scope.
Issue and pull-request records
Repository writes and workflow dispatches need a deliberate permission and approval policy.
Authentication API key
An Atlassian site, API credentials, project identifiers, and access to the selected issue types.
Issue records
Validate the authentication contract, field format, and workflow transitions for your Jira instance.
Authentication OAuth 2.0
An installed application, shop domain, selected API scopes, and inventory location identifiers.
Orders, products, and customer records
Confirm the currently supported API version and restrict inventory writes to an approved workflow.
Authentication Instance-specific setup
A store URL and credentials configured for your WooCommerce authentication contract.
Commerce adapter definition
The definition has no OAuth authorization or token URL. Resolve the store’s authentication setup before connecting.
The Daraja adapter definition includes STK push and transaction-status operations. The configured source endpoint is a sandbox.
The source contains invoice-submission and tax-identifier adapter definitions. That does not establish certified production compliance.
Registered external actions and sync definitions connect application context to a configured company connection.
Event triggers, subscriptions, delivery records, and replay interfaces support workflows that continue across systems.
Authenticated API endpoints and MCP client/server interfaces expose capabilities to other applications and registered tools.
Scope the business outcome, identify the controls, and define what a successful pilot must prove.