Backend integrations, called from a workflow
Connect Slack, GitHub, Google Calendar, LinkedIn, X, Claude, Gemini, OpenAI, Grok, Calendly and Fireflies, then call any of them as a step in a workflow.
Connect Slack in a minute
The same connection, made from the dashboard or the CLI.
The Anythink dashboard
Pick Slack in Integrations, sign in and allow access.
The Anythink CLI
One command opens the OAuth flow and stores the connection.
Claude, through MCP
Ask the assistant to list connections or use one in a workflow.
you › “Which integrations are connected in this project? Add a step to my new-order workflow that posts the order total to #sales on Slack.”
- ✓Listed the project's connections, including Slack
- ✓Added an Integration step to the new-order workflow
- ✓The step posts the order total to #sales
Integrations, wired into workflows
13 seeded providers, callable as workflow steps, with per-user or per-project connections.
13 providers, seeded into every project
Google (sign-in), Google Calendar, Slack, GitHub, LinkedIn, X, Apple (sign-in), Claude, Gemini, OpenAI, Grok, Calendly and Fireflies, each with its own auth type and operations.
In practice
Connect a provider, then call it from a workflow
anythink integrations list
What you can build
A per-user social publisher
Each user connects their own LinkedIn and X account. When they publish a post from your app, a workflow posts it through their connection, not a shared company account.
A Slack-notified support queue
A new support ticket triggers a workflow that posts to Slack and opens a tracking entry. Your team never has to poll a dashboard for new tickets.
An AI-assisted triage step
Summarise a long support ticket with Claude, Gemini, OpenAI or Grok as a workflow step, then route the summary into Slack or GitHub, without hand-rolling an API client for each provider.