Agentic FabriqIntegration Catalogue
Every connector Agentic Fabriq ships, what it exposes, and how a connection to it is made.
A tool is the unit you grant
Each row's tool count is the number of individually grantable MCP tools that integration exposes — slack_send_message is one, slack_list_channels is another. You grant tools, not whole products, so an agent allowed to read Slack cannot post to it.
The three connection methods
Not every provider supports every method, and the table below is explicit about which ones each supports. Whichever is used, the resulting credential is stored in Agentic Fabriq's vault and never returned to your backend.
The fastest path: the user signs in at the provider and approves, with nothing to register and nothing to paste. Usage counts against Agentic Fabriq's app at that provider — which for metered APIs (X, for example) means Agentic Fabriq is billed for the calls and the rate limit is shared.
You register an app at the provider and give Agentic Fabriq its client ID, secret and redirect URI. The OAuth flow is otherwise identical. You get your own rate limit and your own bill, which is the right choice for anything high-volume — and for Salesforce and Zendesk it is the only choice, because neither issues the kind of cross-account app the shared path would need.
Some products have no OAuth flow worth running. For those, the credential is pasted once — a personal access token, a restricted API key, an account SID and key pair. There is no authorization round trip: submitting the credential is the handshake, and Agentic Fabriq validates it against the provider before storing it.
Every integration
Every connector has its own page in these docs, with its actions, scopes and connection methods. Use the connector search in the sidebar to jump straight to one.
Tool names
MCP tool names are {provider}_{verb}_{object}, using the provider key from the table above. Google surfaces carry a google_ prefix on top of it.
| Integration | Example tool name |
|---|---|
| Slack | slack_send_message |
| GitHub | github_create_pull_request |
| Gmail | google_gmail_list_messages |
| Google Drive | google_drive_list_files |
| Microsoft Outlook | microsoft_outlook_list_messages |
| Notion | notion_search |
| Linear | linear_list_teams |
| Stripe | stripe_get_account |
| Salesforce | salesforce_soql_query |
| Snowflake | snowflake_list_databases |
| Datadog | datadog_list_monitors |
| Shopify | shopify_list_products |
| QuickBooks Online | quickbooks_get_company_info |
| X (Twitter) | twitter_get_me |
| Replit | replit_apps_list_apps |
The authoritative list for an agent is always the one it gets back from list_tools, which returns only the tools that survive the intersection of the agent's grants, the user's grants, and the tools the connection's scopes actually cover.
Not in the catalogue?
The catalogue is the set of connectors Agentic Fabriq maintains. Anything else reaches your agent through the same governance layer via a custom integration:
Need help?
Our team is here to help you get started.