Connector guide
Connect Slack to your AI agent
Connect team conversations and channel workflows.
Source checked 2026-09-09. These examples were checked against the linked source revision. They are not a claim of live API verification; your deployed version may differ.
Authentication methods
- OAuth 2.0
Open the local console, select a provider, and configure its credentials. OAuth providers require an OAuth app you register with that service.
Credentials & OAuth →What to check for this connector
This example lists channels available to the connection. Check its required scopes and account access; a missing channel does not by itself prove the connector is broken.
Inspect the Action before calling it
Example purpose
List Slack channels available to the connection.
Required Action scopes
channels:read
Read the schema from your running instance. Check required input, permissions, and the account connection before execution.
curl -s http://localhost:3000/v1/actions/slack.list_channelsAfter connecting an account, adapt the example input to your resources. Add a runtime bearer token if runtime authentication is enabled.
curl -s -X POST \
http://localhost:3000/v1/actions/slack.list_channels \
-H 'content-type: application/json' \
-d '{"input":{"limit":5}}'Read the result
HTTP runtime responses use success, message, data and meta. Inspect success and the Action’s output schema, not just the HTTP status. When execution metadata includes executionId, use it to find the corresponding redacted run log. The example below illustrates the envelope; it is not a live API result.
{
"success": true,
"message": "OK",
"data": {},
"meta": {}
}If the call fails
- For an authentication failure, check the endpoint and credential type: admin access protects /api; a runtime bearer token authorizes /v1 and /mcp. A provider API key is not a runtime token.
- For a permission denial, check the Action’s required scopes, runtime Action rules and connection grants. A valid token may still be forbidden from using the selected account.
- For empty or missing results, confirm the connected account and its access to the requested resource. Successful authorization does not grant access to every workspace, channel or document.
- Inspect the error and run log before retrying. If an Action changes provider data, check whether it already completed; do not blindly repeat the request.
Verification
Catalog entries, local executors, and upstream API verification are separate states. Check the source and verification notes for the Actions you plan to use.
Source checked 2026-09-09· These examples were checked against the linked source revision. They are not a claim of live API verification; your deployed version may differ.
Next steps
For supported providers, OOMOL handles OAuth app configuration and the hosted runtime. You still choose the account and approve its permissions.
Explore Connectors →