Integration

Connect Slack and Teamwork

When New Mention (instant) fires in Slack, your agent runs Complete Task in Teamwork, or New Project in Teamwork to Send Direct Message in Slack. Describe the whole flow and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Slack and Teamwork to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Connecting Slack and Teamwork gives project work a home in chat: new Teamwork projects, tasks and milestones can show up in the right Slack channel, and messages or reactions in Slack can create and close Teamwork tasks. The agent builds the whole flow, tests every scenario against your real channels and projects, and keeps it running.

Example flows

What Slack and Teamwork can do together

From Slack to Teamwork

From Teamwork to Slack

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Slack and Teamwork

Triggers and actions 21 triggers · 82 actions

Each app on its own

Reviews

What our customers say

More from Slack

More into Teamwork

Questions

Slack and Teamwork, answered

Can a new Teamwork project get its own Slack channel automatically?

Yes. The New Project trigger in Teamwork can create a channel in Slack, set its topic and post an opening message with the project details. The agent can first read the project back with Get Project so the channel is named and described from the real record.

Can people close Teamwork tasks from Slack?

Yes. A reaction added to a message in Slack can mark the linked task complete in Teamwork using the Complete Task action. The agent tests each scenario so only the emoji you choose triggers it, and other reactions are left alone.

What can start an automation from Slack?

Any of Slack's 15 triggers in the catalog, including New Mention (instant), New Reaction Added, New Channel and New Channel (instant). Describe the moment in plain language and your agent picks the right one.

What can your agent do in Teamwork when something happens in Slack?

Any of Teamwork's 22 actions, including Complete Task, Create Task, Get Project and Create Project. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Teamwork to Slack?

Yes. When something happens in Teamwork, your agent can act in Slack too. This page covers both directions: Teamwork's triggers and Slack's actions are listed here as well.

Do I have to build a connector for Slack or Teamwork?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

Can my AI client use Slack and Teamwork without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.