Workflow map: find where your tools' AI runs out

Each tool's built-in AI is like a team member who only works in one room. Inside it, they're sharp. My take: the work gets dropped in the hallway between rooms.

This guide gives you a one-page map to find those hallway gaps in one workflow. If the map shows a gap, you connect Slack and ClickUp to Claude (each link is called a connector) with approval on and Claude's mode on Manual, so nothing is created or sent without your OK.

Do it with Claude

Let Claude map your workflow

It asks about one workflow, then fills in your map.

Copy
Paste into Claude
Answer, get your map

See the prompt Claude gets

You are my setup coach. I run a small business and do not code. Use plain words and short sentences. The guide is pasted under this prompt. Use it as your script and your source of facts. I am reading it too, so do not summarize it and do not read its steps back to me. The guide mentions a card at the top, screenshots, and steps that tell me to paste a prompt. Ignore those: this message is that card, and I already pasted it. The guide's finished map is an example only, so reuse nothing from it. Task: interview me about one workflow I repeat every week, then fill in the guide's map table. Use the guide's prompt titled "Map my workflow" for the table columns and rules, but I have not filled in its curly braces, so ask me instead. Ask which tools and plans I use. Write "Unsure: check the vendor's docs" for any built-in feature you cannot confirm, and never guess a feature. Ask 3 to 5 basic questions first, as clickable choices if you can (in Claude Code, use the AskUserQuestion tool), else lettered options: the kind of workflow, how it starts, which tools, which plans, and who does the steps. I can always type my own answer. Then ask me to describe the workflow in my own words. Then ask numbered follow-ups, 3 at most per message. Do not move on until you are fully clear. Never invent. Use (check) only for facts I gave you that are unclear. Before you draw the table, play back the steps you understood and wait for my yes. After 10 questions (count every question you ask me), pause, ask if we should continue, and wait for my answer before you do anything else. If I say "enough, map it", stop asking and show me what you have. After the map, recommend connectors only for real gaps between my actual tools. If there is no gap, say "Nothing new needed. Keep what you pay for." and stop. If there is a gap, you cannot connect anything for me, so walk me through the guide's connector chapters one step at a time, with approval on. They cover only Slack and ClickUp. For other tools, check the connector directory with me and never invent steps; if there is no connector, mark that step manual. Only call a connector relevant after I confirm it is for the exact tool named in that step. Use the guide's "First safe test request" only at this stage, and ask me for its curly-brace values then. Go one step at a time and wait for me to say "done" after each step. Say what my screen should show. If it looks different, help me fix it. Never ask for passwords or API keys. Warn me about costs and ask first. Start now: put your first basic questions in this same reply, not just a promise to ask them. Use the guide's menu and button names word for word, not your own. Do not wait for me to say go.

When you copy, the whole guide goes in under this prompt, so Claude has every step.

Rather do it by hand? Jump to the steps

01 / 07

Map one workflow

Start with one handoff you do every day, such as a request that moves from Slack to ClickUp, and map the workflow around it. Fill the table below, one row per step. Four rows is a good start and three to seven is enough. Add rows if you need them.

5: columns in the map
1: workflow to start with
45 min: with connectors

Write each step from "request arrives" to "done", one row each, with its number.
Name the tool where the step happens. A step that moves between tools gets both names.
In "Built-in AI covers it?", write Yes, Partly, No or Unsure. If you don't know what a tool's AI can do, write Unsure and check it later on the vendor's page.
In "Crosses tools?", write one of three answers. Yes, GAP: the step moves between tools. No, COVERED: it stays in one tool and that tool's AI does it. No, MANUAL: it stays in one tool and its AI can't do it. If the AI column says Unsure and the step stays in one tool, write Unsure here too.
In "Needs your approval?", write Yes if the step creates a record, sends a message, or reaches a client. Otherwise write No.

The handoffs are where the gaps live. A handoff is where work moves from one tool or person to another. Slack's workflow mapping guide agrees.

Step	Which tool	Built-in AI covers it?	Crosses tools?	Needs your approval?
1	empty	empty	empty	empty
2	empty	empty	empty	empty
3	empty	empty	empty	empty
4	empty	empty	empty	empty
5	empty	empty	empty	empty

Row 1 of 5

Step: empty
Which tool: empty
Built-in AI covers it?: empty
Crosses tools?: empty
Needs your approval?: empty

02 / 07

See a finished map

Here is a made-up request. A client asks in Slack for a Saturday post. As of September 2026, this is what each tool's AI covers.

Step	Which tool	Built-in AI covers it?	Crosses tools?	Needs your approval?
1. Client asks in Slack for a Saturday post	Slack	Yesthread summary (Slack Pro and up)	Covered	No
2. Request becomes a ClickUp task with an owner and a date	Slack to ClickUp	Partly/clickup new makes the task, you pick list, owner and date	Gap	Yescheck the draft
3. Short brief written on the task	ClickUp	YesBrain AI Writing	Covered	Yesa person reads it
4. Daily digest posted to the team	ClickUp to Slack	PartlyClickUp's AI agents can send Slack messages on a schedule, plan permitting	Check	Yesat first, it sends a message

Step 1 is covered. Slack AI summarizes the thread.

Step 2 is a gap. Creating a task in another app is not part of Slack AI's summary feature. ClickUp's Slack integration lets you type /clickup new to turn a conversation into a task. A person still reads the request and picks the list, owner and date. If that already does what you need, keep it and skip the connector.

Step 3 is covered. ClickUp Brain includes AI Writing.

Step 4 needs a check. ClickUp's AI tools page lists a scheduled trigger and a Slack send action for its AI agents, so check your plan. Its Slack integration documents task-update notifications, not a daily digest.

One sure gap, one to check. The setup below fixes step 2. Step 4 needs Claude to send a message, so this guide leaves it alone. Your own map may show no gaps.

DiagramDo you need anything new?

Is every step covered?Look at your finished map

Yes

Keep what you pay forNothing new needed

Does the gap cross tools?

Check that tool's own AIIt may already do this

Yes

Add a connectorOne assistant across both tools

Is every step covered? If yes, keep what you pay for.
If no: does the gap cross tools?
If it does not cross tools, check that tool's own AI.
If it crosses tools, add a connector.

Fig 2.1Do you need anything new?

03 / 07

Let Claude draft your map

The "Do it with Claude" card runs this same prompt for you. Paste it yourself if you'd rather.

You don't need to connect anything for this part. Fill in what you know about one workflow, the way you'd brief a new hire, and leave the rest. Paste the prompt into Claude and it interviews you. Typing your own answer always works, even when Claude shows clickable choices.

Map my workflow

I want to map one workflow to find where each tool's built-in AI covers a step and where it does not. Starting info. Fill in what you know. If a field is still in curly braces, ask me about it. My workflow, in my own words: {DESCRIBE THE WORKFLOW: who asks for what, where, and what happens until it is done} The tools involved: {LIST EVERY TOOL, for example Slack, ClickUp, Gmail, Google Sheets} The plans I am on, if I know them: {PLANS, for example Slack Pro, ClickUp Unlimited, or "not sure"} How to interview me: 1. Ask 3 to 5 basic questions first, as clickable choices. Number your questions as you go, without a total ("Question 4", not "Question 4 of 10"). In Claude Code, use the AskUserQuestion tool so I can click my answers. If you cannot, give lettered options (A, B, C) and I will type a letter. 2. Then ask numbered follow-ups, 3 at most per message. Offer likely options. Never guess a feature or menu name. 3. Do not draw the table until it is clear. If I am vague, ask for a real example from last week. 4. When it is clear, play back the steps you understood as a short numbered list. Ask "Is this right? What is missing?" Wait for my yes. If I correct you, fix the list and play it back again. 5. After 10 questions (count every question you ask me), ask me as a yes or no question whether to keep going, and wait for my answer. If I say "enough, map it", mark anything unconfirmed "Unsure" and go on. After my yes, do this: 1. Break the workflow into 3 to 7 steps, from the request arriving to "done". One action per step. If my description skips a step, add it and mark it "ADDED, please check". 2. Fill in this table, one row per step, with these columns: Step (the number and what happens) | Which tool | Built-in AI covers it? | Crosses tools? | Needs your approval? Which tool: where the step happens. If it moves from one tool to another, write "Tool A to Tool B". Built-in AI covers it?: write Yes only if you know that tool's own AI feature does this step on my plan, Partly if it does only part of the step, No if you know it cannot. If you are not sure, write exactly "Unsure: check the vendor's docs" and nothing else in that cell. Write a Yes, Partly or No only when you are sure. You may add the feature name after a colon, as in "Yes: thread summary (Slack Pro and up)". When in doubt, write the Unsure line. Never guess a feature or a plan limit. Crosses tools? (use only one of these three answers, word for word): write "Yes, GAP" if the step starts in one tool and ends in another, or if a person copies, retypes or re-picks something between them. Write "No, COVERED" if it stays in one tool and that tool's AI handles it. Write "No, MANUAL" if it stays in one tool but its AI cannot do it. If "Built-in AI covers it?" says Unsure and the step stays in one tool, write "Unsure" here too: no COVERED or MANUAL until the AI answer is known. Needs your approval?: Yes for any step that creates a record, sends a message, or reaches a client. Say what a person should check. 3. Under the table, list the gaps in order. For each, say in one sentence what a person does by hand today. 4. If there are zero gaps, end with: "Nothing new needed. Keep what you pay for." Use plain words. Use role names, not client names. Do not invent product features.

Claude writes "Unsure" where it doesn't know. Check each Unsure row on the vendor's page.

04 / 07

Connect Slack and ClickUp to Claude

DiagramOne assistant across the gap

1Request lands in SlackSlack

Slack connector

ClickUp connectorAsks before creating

2Task with owner and dateClickUpNow covered

A request lands in Slack.
Claude reads it through the Slack connector.
Claude drafts the ClickUp task and asks you before creating it.
Through the ClickUp connector the task is created with an owner and a date. Step 2 is now covered.

Fig 4.1One assistant across the gap

A connector is a key card you hand Claude for one app. It opens that app with your own login, so Claude can do only what you can. With a key card for Slack and one for ClickUp, Claude can cross the hallway between them.

Connectors belong to your Claude account. Connect once and they show up on the web, in the desktop app and in Claude Code, when you're signed in to that account (Anthropic's connectors page, Claude Code docs). For a separate AI user with limited access, use the give your AI its own login guide. A tool you already connected as the AI user stays on that user's limited access.

Do this part on a computer, with Claude's settings open in another window. The pictures show the desktop app. Skip it if your map shows no gaps.

The Slack and ClickUp connectors come from Claude's directory, and directory connectors work on every Claude plan, per Anthropic's support page. On Team or Enterprise, an Owner may need to turn a connector on first. Your Slack Workspace Owner or app manager may also have to approve it.

Both connectors are official. Slack's claude.com listing carries an "Anthropic verified" label, and inside Claude a verified connector shows a green tick next to its name. Anthropic's own advice applies: "Only use connectors from developers you trust." See the Slack listing and the ClickUp listing. As of September 2026, ClickUp labels its connector public beta.

Connect Slack

Slack

At a glance

Signs in as: You
Approval: Your Slack Workspace Owner or app manager may need to approve
Time: About 5 minutes

In the side panel of Claude, click Customize. It is the page that holds your connectors, skills and plugins.
Click Connectors.

The Claude Customize page with the Connectors tab selected, next to Skills and Plugins, and the Yours and Discover switch below them — Fig 4.2What you should see after step 2

Click Discover.
Search for Slack.

The Discover view in Claude after searching for Slack. The Slack card is the first result, with a green tick — Fig 4.3What you should see after step 4

Click Connect to Claude. Slack opens a screen asking you to sign in and approve access.

Read the access list.
Approve access. Slack now shows as connected in Connectors.

Illustration · as of Oct 2026

Fig 4.5Illustration of Slack connected in Claude after step 7

Seeing Request instead of Connect? See "If it breaks".

Connect ClickUp

ClickUp

At a glance

Signs in as: Your ClickUp login
Daily limit: 100 to 300 requests
Time: About 5 minutes

Click Discover again.
Search for ClickUp.
Click Connect to Claude.
Sign in to ClickUp with your normal login. There is nothing to copy or paste.
Approve access.
If ClickUp asks which workspace, pick the one where you'll create your "Claude test" list later.

Illustration · as of Oct 2026

Fig 4.6Illustration of ClickUp asking which workspace, at step 6

Go back to Claude. ClickUp now shows as connected next to Slack.

Illustration · as of Oct 2026

Fig 4.7Illustration of Slack and ClickUp connected after step 7

05 / 07

Keep approval on

Connectors sort their tools into groups, such as Interactive tools, Read-only tools and Write/delete tools. Claude lets you choose Always allow, Needs approval, or Blocked for a whole group or for a single tool. As of October 2026.

Slack's Write/delete tools group holds Send message, Schedule message, Create a canvas and Update a canvas. Its Interactive tools group holds Create a draft message. A scheduled message goes out later while you aren't watching, so it needs approval like Send message.

Group or tool	Examples	Set it to
Write/delete tools group	Slack: Send message, Schedule message, Create a canvas, Update a canvas. ClickUp: all 34, including create, update and delete	Needs approval
Two ClickUp tools inside that group	Delete Task, Delete Comment	Blocked
Read-only tools	Tools that only read or search	Needs approval first. Always allow once you trust it.
Interactive tools	Slack: Create a draft message	Needs approval first. Always allow once you trust it.

Pro tip: if you connected Slack, set its private-search tool to Blocked before you move any reads to Always allow. The Slack guide shows how.

On Team or Enterprise, an Owner uses the same page (Customize › Connectors › the tool) to limit actions for the whole organization, and individual users can't override it (Anthropic).

ClickUp's connector creates and updates tasks, comments, time tracking and lists, and it can delete. As of October 2026, ClickUp's Write/delete tools group has 34 tools, including Delete Task and Delete Comment. Set those two to Blocked, and try everything in a test list first.

Set the permissions

Open Slack in your connector list (Customize › Connectors › Slack).
Find the three tool groups: Interactive tools, Read-only tools and Write/delete tools.
Set the whole Write/delete tools group to Needs approval.
Set Read-only tools and Interactive tools to Needs approval.
Open ClickUp in your connector list.
Set the whole Write/delete tools group to Needs approval.
Inside that group, set Delete Task and Delete Comment to Blocked.
Set the other tool groups, such as Read-only tools, to Needs approval.
Check the mode. If your message box has a permission setting, set it to Manual. If it still shows separate Chat and Cowork options, pick Manually approve in Cowork. If you see neither, Claude asks with an Allow once or Always allow prompt.

Illustration · as of Oct 2026

Fig 5.1Illustration of ClickUp's tool permissions after step 8

Run a zero-risk test

In ClickUp, create a list named "Claude test".
In Slack, create a private channel with only you in it.
Post one fake request in that channel, for example "Can we add a Saturday menu post?"
In Claude, start a new chat.
Click + ("Add files, connectors, and more") at the lower left of the message box.
Click Connectors.
Toggle Slack and ClickUp on.

Illustration · as of Oct 2026

Fig 5.2Illustration of the + menu with Slack and ClickUp on, after step 7 (newer screens show Manual in the message box)

Paste the prompt below. Replace {TEST CHANNEL} with the name of your private channel, without the # sign.

First safe test request

Read the latest message in #{TEST CHANNEL}. Draft one ClickUp task for it in the list "Claude test". Include a title, a due date and a two-line brief. Assign it to me. Show me the draft before you create it. Do not send any Slack message, and do not change any other task.

272 characters

If Claude asks before a read, click Allow once each time.
Read the draft. Nothing exists in ClickUp yet.
Reply: Create it.
When Claude asks to create the task, click Allow once.

Illustration · as of Oct 2026

Fig 5.3Illustration of the approval prompt at step 12 (newer screens show Manual in the message box)

Open the "Claude test" list in ClickUp and look for the task.

Confirm the setup works:

Do this now0 / 8 done

Slack and

ClickUp both show as connected in Customize › Connectors

Slack's Write/delete tools group is set to Needs approval

ClickUp's Write/delete tools group is set to Needs approvalDelete Task and Delete Comment are set to Blocked in

ClickUp

Claude's mode is Manual (or Manually approve, if Cowork is still a separate option for you)

Claude showed me a draft before anything was createdAn approval prompt appeared and I chose Allow onceThe task is in my "

Claude test" list and assigned to me

06 / 07

If it breaks

I see Request instead of Connect. What now?

Someone else has to approve it. On Team or Enterprise that is a Claude Owner, per Anthropic's getting-started page. On the Slack side, workspace admins can approve and manage MCP client integrations. Slack's app approval is off by default, but Slack's Claude page lists admin approval as a prerequisite, so if you aren't the Workspace Owner, ask them first. Send them the listing link and say what you'll use it for: read requests, and draft tasks with approval on.

ClickUp stops answering partway through the day.

You may have hit the daily request cap. As of October 2026, without the Everything AI add-on, ClickUp allows 100 requests per 24 hours on Free, 300 on Unlimited, and more on higher plans. Check ClickUp's MCP page for current limits.

ClickUp's own Slack integration already makes tasks. Why add Claude?

It makes the task, but you pick the list each time. Users on ClickUp's feedback board report that attachments don't carry over. They also report it is set up per channel and per Space. If that is fine for you, keep it.

How do I switch it off?

In Claude, open Customize › Connectors, open the tool and click Disconnect. For Slack, also remove your sign-in in Slack (steps).

Finish line

What to do next

Use the "Do it with Claude" card, or the "Map my workflow" prompt, on one workflow you repeated this week.

If it finds no gaps, close this page and keep what you pay for. If it finds one, come back to "Connect Slack and ClickUp", then do "Keep approval on".

You reached the end of the guide