The 9 Best AI Connectors for Agencies in 2026 (Claude and ChatGPT, Ranked for Client Work)

Key Takeaways

• Storyflow ranks first for agency client work because it is the connector here where Claude or ChatGPT builds the whole client-facing plan, not one asset: the brief becomes a board, the board becomes a deck, and the client opens the link with no account.
• An agency connector stack has three layers: where the inputs live (Google Drive, HubSpot), where the plan and pitch live (Storyflow), and where production happens (Canva, Figma, Asana, Slack). Most agencies connect the first and third layers and skip the middle one.
• Every connector on this list works in Claude. Storyflow, Canva, Figma, Asana, HubSpot, Google Drive, Notion and Miro also document a ChatGPT route; Slack's official docs cover Claude, Claude Code and Cursor.
• Scope every connector to one client where the tool allows it. Storyflow asks at sign-in which projects the assistant may use and whether it may make changes, so a connection can be limited to one client's project, read-only.
• Storyflow's MCP server has no action limit on Plus, Pro or Max. A free account (today, one a paid member invited) gets 25 actions a week, and the server runs on your own assistant's model, so it spends no Storyflow AI credits.
• A solo studio can run the core stack (Claude Pro, Storyflow Plus, Google Drive, Canva Free) for about $25 a month on annual billing. The biggest line item for a 6-person agency is assistant seats, not connectors.
• Storyflow is the wrong pick for formal versioned approvals, sending or scheduling posts, invoicing, or anything offline: it is browser-only and paid-only during early access.

Why Agencies Need Connectors, Not Another Chat Tab

You paste the client brief into ChatGPT, get a sharp concept back, then spend the next 90 minutes copying it into a deck, a task list, a Slack thread and a shared folder. The thinking took ten minutes. The moving took the afternoon. That gap is what connectors close, and it is wider in an agency than anywhere else because every piece of work has an audience outside the building.

Client work has an audience the chat never sees

A chat transcript is private by design. A client brief is the opposite: it starts in the client's inbox, passes through a strategist, a designer and an account lead, and ends in front of the client again as a concept, a deck or a set of assets. A connector earns its place in an agency when the assistant's output lands somewhere the client or the team can open without you re-typing it. Read-only connectors that fetch context are useful. Connectors that write the deliverable are the ones that save the afternoon.

The brief is scattered across four tools before anyone starts

The brief is a PDF in Google Drive. The budget and contact history sit in HubSpot. The brand kit lives in Canva or Figma. Last month's feedback is a Slack thread. An assistant with no connectors sees only what you paste, which is usually the brief and nothing else, so the first draft ignores the budget, the brand rules and the feedback that killed the last round. The fix is not a longer prompt. It is giving the assistant read access to where those inputs already live.

Agencies carry a data-separation duty most teams do not

An in-house team has one brand. An agency has eight, and some of them compete. A connector that grants your assistant access to "everything your account can see" means a question about Client A can surface Client B's launch plan. That is why permission scoping per client is one of the six ranking criteria below, and why the setup section tells you to connect per client where the tool supports it.

How We Ranked the Connectors

We judged every connector on the work an agency actually ships: a brief in, a concept out, a client review, then production. The criteria are specific to client work, and the weighting is published so you can re-score with your own priorities. Every connector was checked against the vendor's own documentation on October 9, 2026, and each source is linked in its review.

Brief-to-deliverable reach (25%)

Can the assistant take a client brief through this connector and produce something a client or teammate opens directly: a board, a deck, a design, a task list? Connectors that only retrieve files score lower here than connectors that build the output.

Client-facing output and sharing (20%)

Is what the assistant builds presentable to a client, and can you share it without forcing the client to create an account? A deck a client opens from a link beats a file you have to export, attach and re-send after every change.

Write depth (20%)

How much can the assistant change through the connector: create, edit, move, or only read? We scored what the vendor documents, not what a demo implies.

Permission scoping per client (15%)

Can you limit the connection to one client's project or workspace, and can you connect read-only? For agencies holding several clients' plans, this matters more than any feature.

Availability in Claude and ChatGPT (10%)

Agencies rarely standardise on one assistant. A connector that works in Claude and in ChatGPT, documented by the vendor, scores higher than one that only reaches coding tools.

Cost for a small agency (10%)

What it costs a 2 to 10 person agency to use the connector at all, including any plan the vendor requires. Free connectors on paid seats you already own score well.

How the scores add up

What we did not weigh: raw design quality, CRM depth or task-management features on their own. Those decide which production tool you buy. This list ranks how much each tool does once your assistant is connected to it.

Comparison Table: The 9 Best AI Connectors for Agencies in 2026

Storyflow leads on brief-to-deliverable reach and client sharing. Google Drive leads on context: almost every agency brief already sits in it. Canva leads on finished, on-brand production assets. The ranking is not "which tool is best". It is which connector does the most of a client job once your assistant can reach it.

The 9 Best AI Connectors for Agencies, Reviewed

1. Storyflow

The verdict: the connector that turns your assistant into the person who builds the client plan, not just the person who writes about it.

Best for: agencies and studios that take a client brief to a concept, a pitch deck and a plan the client can open.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly, adds AI image generation), Max $39 ($49 monthly, adds a team workspace with roles and permissions). Paid-only during early access; a Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. The MCP server has no limit on paid plans. See Storyflow pricing.

Storyflow is a visual project planning workspace for creative work: an infinite canvas that holds notes, tables, documents, images, moodboards, storyboards, mind maps, kanban, charts and slide decks. Its MCP server lives at https://mcp.storyflow.so/mcp and works with Claude, ChatGPT, Gemini, Grok, Claude Code, Cursor and any assistant that can add a remote MCP server. The Storyflow MCP page has the overview, the Storyflow for agencies page shows the agency boards, and the connection guide has the exact steps per assistant.

It ranks first because it does the part of agency work the other connectors leave to you. Hand Claude a client brief and ask for a board, and the assistant creates the project, builds the plan in groups and tables, lays out a mind map of the concept territories and adds a slide deck next to the plan it came from. What it adds appears live on an open board, and clients that support MCP apps can show the live board inside the chat. The client opens a view-only link with no account, and signs in to comment. On Monday, you ask "what changed on the client board in the last week, and who changed it?" and get a plain answer instead of opening every frame.

Strengths:

• Builds client-facing output: notes, groups, tables, charts, diagrams, mind maps, documents, slide decks, shot cards, strip boards, colour palettes and carousel pages, and applies Storyflow board templates.
• Per-client scoping at sign-in: pick which projects the assistant may use, and whether it may make changes. Without changes it can only read.
• Reads what changed on a board and who changed it, which is the account lead's Monday question.
• No MCP limit on Plus, Pro or Max, and the server runs on your assistant's model, so it spends no Storyflow AI credits.

Limitations:

• A photo you attach in the chat does not reach Storyflow; the assistant gives you an upload link for the board instead.
• No formal approval button or versioned proofing, no publishing or scheduling of posts, no invoicing.
• Browser only: no native desktop or mobile app and no offline mode.
• ChatGPT needs Plus or above with developer mode on; on Business and Enterprise an admin turns developer mode on.

Try it: connect Storyflow to Claude with Customize, Connectors, Add, Add custom connector, name it Storyflow, paste the address, Continue, Sign in now, Add. Then paste your next client brief and ask for the board.

2. Google Drive

The verdict: the context connector every agency should add first after its planning tool, because it is where the brief already is.

Best for: giving the assistant the client brief, brand guidelines, research and last year's work without pasting any of it.

Pricing: the connector is included with Claude and ChatGPT; you need a Google account with access to the files.

Anthropic's Google Workspace connectors article says Claude can search and retrieve Docs from your Drive, read Sheets, Slides, PDFs and Office files (text only; embedded images are not processed), create folders, upload files and save Claude-generated files to Drive, and share, move or trash files with approval required by default. On Team and Enterprise plans, an Owner must enable the connectors for the organisation first. On ChatGPT, OpenAI's Google Drive app article describes searching and referencing files your Google account can access, following your existing Drive permissions.

It ranks second because nearly every agency brief starts as a Drive file, and an assistant that can read the brief, the brand book and the last campaign's wrap report writes a better first concept than one working from a pasted paragraph. It does not rank higher because Drive is an input: the output still has to land somewhere the client sees.

Strengths:

• Reads the formats agencies actually receive: PDFs, Slides, Sheets and Office files.
• Follows the Drive permissions you already manage per client folder.
• Claude can save generated files back to Drive.

Limitations:

• Text only: the assistant does not see images inside documents, which matters for brand books.
• OpenAI notes Shared Drives are not included in the initial Library experience, and chat search availability varies by ChatGPT plan.
• Scoping is by Google account, not by client; a broad account sees every client folder.

3. Canva

The verdict: the strongest connector for producing finished, on-brand assets from a chat.

Best for: social carousels, one-pagers and presentation exports once the concept is approved.

Pricing: Canva says its AI Connector is available on all Canva plans, including Free; resizing needs a paid plan, and Brand Templates with autofill are limited to Enterprise, per Canva's AI Connector page.

Canva's AI connectors help page describes connecting ChatGPT, Claude, Gemini and Microsoft Copilot to Canva, then searching Brand Templates, autofilling them and exporting files, depending on your plan and assistant. Canva's newsroom describes creating and editing designs inside ChatGPT and searching existing decks and documents. A team admin controls the connector: when it is off, nobody on the team can connect an assistant.

Canva ranks third because it turns a concept into the thing that gets posted. Where it falls short for agency planning is the stage before production: a Canva design is a finished artefact, not the place where a strategist works out three territories, the audience and the rollout. Use Storyflow to decide what to make and Canva to make it.

Strengths:

• Finished, exportable assets from a prompt, on any Canva plan.
• Works across ChatGPT, Claude, Gemini and Copilot.
• Team admin control over whether anyone can connect an assistant.

Limitations:

• Brand Template autofill, the most useful agency feature, is Enterprise only.
• Built for finished designs, not for a strategy board with research, tables and a plan.
• Canva's newsroom describes the ChatGPT app rolling out outside the EU first, so check availability in your region.

4. Figma

The verdict: the connector for agencies whose deliverables are design files and websites.

Best for: design and digital agencies handing designs to developers, and quick FigJam diagrams in a pitch.

Pricing: Figma's help article says the remote MCP server is available on all seats and plans. Figma's pricing page lists Professional at $16 a month for a Full seat, $12 for a Dev seat and $3 for a Collab seat.

Figma's developer documentation says the server gives agents design context (variables, components, layout data) and can create and modify native Figma content directly from an MCP client. The remote server address is https://mcp.figma.com/mcp, and Claude Desktop and Claude Code support it. Separately, the Figma app in ChatGPT builds editable FigJam diagrams from a conversation, on any Figma plan, outside the EU.

Figma ranks fourth because for a design agency it is the production surface, and its write support is genuine. It scores lower on client-facing planning: a FigJam flowchart helps a pitch, but the brief, budget, timeline and concept deck do not live naturally in a design file.

Strengths:

• Writes native Figma content, not just reads it.
• Remote server on every seat and plan.
• FigJam diagrams from ChatGPT for process maps and launch Gantt charts.

Limitations:

• Only clients listed in Figma's MCP catalog can connect.
• Most of its documented value is design-to-code, which matters less to a content or campaign agency.
• The ChatGPT app is not available in the EU.

5. Asana

The verdict: the connector that turns an approved plan into assigned tasks.

Best for: agencies that already run delivery in Asana and want the assistant to create and report on tasks.

Pricing: Asana's pricing page lists Personal free for up to 2 users, Starter at $10.99 per user a month billed annually ($13.49 monthly) and Advanced at $24.99 ($30.49 monthly).

Asana's MCP documentation says the server at https://mcp.asana.com/v2/mcp lets assistants create and manage tasks and projects, generate reports and analyse project data, with apps for Claude and ChatGPT. Workspace app management can block a client app, and Enterprise+ customers can allow or block MCP clients.

Asana ranks fifth because the task list is the step after the creative decision. Once the client approves a concept on the board, asking Claude to create the 14 production tasks in Asana with owners and dates is exactly the kind of re-typing connectors should remove. It ranks below the creative tools because tasks are not what you show a client.

Strengths:

• Creates and manages tasks and projects from a chat.
• Status reports from real project data.
• Works in Claude, ChatGPT and coding clients.

Limitations:

• Per-seat pricing grows with the team.
• Tasks are internal; not a client-facing artefact.
• Admin controls over which MCP clients connect are an Enterprise+ feature.

6. HubSpot

The verdict: worth connecting if your client, deal and contact history already lives in HubSpot.

Best for: account leads and new-business teams who want client context in every answer.

Pricing: HubSpot's launch announcement said the ChatGPT connector would be available to HubSpot customers on all tiers who have a paid ChatGPT plan.

HubSpot's AI tools page lists connectors for ChatGPT, Claude, Gemini and Copilot, and says the ChatGPT connector can create and update CRM records and log activities from the chat, while the Claude connector can update the CRM without leaving the conversation. The remote MCP server gives read and write access to contacts, companies, deals, tickets and engagements, with read-only access to campaigns and website pages.

HubSpot ranks sixth because client context makes concepts sharper (the account's budget, the last three calls, what was promised), but it is context and admin, not the creative work. If your agency keeps client records in a spreadsheet or a different CRM, skip it.

Strengths:

• Write actions: create and update records, log activity.
• Works in four assistants.
• Respects the HubSpot user's existing permissions.

Limitations:

• Only useful if HubSpot is already your CRM.
• Sensitive data properties are not accessible through the connector.
• An admin connects the account before others can.

7. Slack

The verdict: the connector for pulling scattered feedback into one place and posting updates.

Best for: agencies whose client and team feedback lives in Slack channels.

Pricing: uses your existing Slack workspace; a workspace admin must approve the MCP integration.

Slack's MCP server overview describes searching channels, sending messages and managing canvases through any MCP client, at https://mcp.slack.com/mcp over Streamable HTTP. Slack's Claude setup guide covers Claude Desktop through Customize, Connectors and Claude Code through a plugin, both requiring admin approval.

Slack ranks seventh because the most useful agency prompt here is retrieval: "summarise every piece of client feedback on the spring campaign from the last two weeks". That is valuable, but it feeds the plan rather than producing it. Slack's docs do not document a ChatGPT route, which costs it points on availability.

Strengths:

• Searches messages and threads across channels you can access.
• Sends messages and creates canvases.
• Admin approval is built in.

Limitations:

• No ChatGPT setup documented by Slack.
• Retrieval is only as good as how disciplined your channels are.
• Not a client-facing surface for most agencies.

8. Notion

The verdict: a solid connector for the agency wiki, SOPs and text-first briefs.

Best for: agencies that keep processes, templates and client notes as Notion pages.

Pricing: Notion's pricing page lists Plus at $10 per member a month billed annually ($12 monthly) and Business at $20 ($24 monthly); Business includes Notion Agent.

Notion's MCP guide says that after authorisation the client can read and update content you can access in the selected workspace, with tools for creating and updating pages, comments and file uploads. Notion is also listed in Claude's connector directory. The guide's documented clients include Claude Code, Codex, Cursor and VS Code, and Notion's help page on Notion MCP names ChatGPT Pro among popular AI apps.

Notion ranks eighth because it is a strong document layer but a weak visual one for client work: a concept with moodboard references, a timeline and a deck is three pages and an export in Notion, and one board in a canvas tool. Notion's own help warns that MCP tools act with your full Notion permissions, which is a scoping concern for agencies holding several clients in one workspace.

Strengths:

• Reads and writes pages and comments.
• Good for SOPs and reusable brief templates.
• Remote server over Streamable HTTP.

Limitations:

• Acts with your full workspace permissions.
• Text-first; weak for visual concepts.
• Notion's help names ChatGPT Pro specifically; check your ChatGPT plan first.

9. Miro

The verdict: the pick when the client's own team already lives in Miro.

Best for: workshop-led agencies and clients with an existing Miro workspace.

Pricing: Miro says its MCP server works on all Miro plans, including free teams.

Miro's MCP documentation lists use cases to summarise and search boards, build boards, generate diagrams and act on comments, and documents clients including Claude, ChatGPT, Codex, Claude Code, Cursor, Gemini CLI and VS Code. Enterprise admins get more security controls.

Miro ranks ninth for agency client work because it is a collaboration whiteboard first: excellent for running a live workshop with a client team, thinner on the documents, tables and decks a concept pitch needs. If your client insists on Miro, connect it; if the board is yours, Storyflow does more of the pitch.

Strengths:

• Works on every Miro plan.
• Builds boards and diagrams from a chat.
• Clients often already have accounts.

Limitations:

• Diagram and sticky-note output more than pitch-ready decks.
• Your assistant needs the board URL in the prompt for most tasks.
• Workshop-shaped rather than brief-to-pitch shaped.

Honorable Mentions and Connectors We Left Out

Several tools agencies use every day did not make the ranked nine. Here is why, so you can decide whether they belong in your stack anyway.

Milanote

Milanote is a well-loved moodboard tool, with a free tier of 100 notes, images or links and 10 file uploads, $9.99 per person a month billed annually, and flat Team pricing at $49 a month billed annually, per its plans page. Its plans page lists no AI features, and we found no connector or MCP server published by Milanote as of October 9, 2026. Until one exists, your assistant cannot build or read a Milanote board, which is the whole point of this list.

monday.com and Box

Both appear in Claude's connector directory: monday.com for projects, boards and dashboards, Box for searching and analysing content. They are good choices if your agency already runs on them; neither does anything for the client-facing plan that the ranked tools do not.

Adobe

Adobe is listed in Claude's connector directory for designing and editing with Adobe creative tools. We did not rank it because we could not confirm from Adobe's own documentation which actions and plans apply, and this list only ranks what vendors document.

Frame.io, ClickUp and Dropbox

We could not confirm an official connector for these in Claude's directory or a vendor MCP page on the day we checked, so they are left out rather than guessed at.

How to Set Up the Agency Connector Stack in One Afternoon

Most agencies add connectors one at a time as someone gets curious, and end up with a stack nobody scoped. Do it in one sitting, in this order, and the permissions are right from day one.

Step 1: Pick one assistant for the team

Choose Claude or ChatGPT as the default. Claude Pro is $17 a month billed annually ($20 monthly) and Claude Team standard seats are $20 a seat billed annually ($25 monthly), per Claude's pricing. ChatGPT Business is $20 per user a month billed annually ($25 monthly) with a 2-seat minimum, per OpenAI's help center. One assistant means one set of connector permissions to manage.

Step 2: Connect Storyflow, scoped to one client

In Claude: Customize, Connectors, Add, Add custom connector, name it Storyflow, paste https://mcp.storyflow.so/mcp, Continue, Sign in now, Add, sign in to Storyflow. In ChatGPT: Settings, Security and login, turn on Developer mode, go to chatgpt.com/plugins, click the plus button, name it Storyflow, choose Public endpoint, paste the address, create, sign in. At sign-in, pick only the client project you are working on, and decide whether the assistant may make changes.

Step 3: Connect Google Drive and check what it can see

Add the Drive connector from your assistant's connector list. Then ask it to list the folders it can reach. If it sees every client, consider a separate Google account or shared folder structure for assistant work.

Step 4: Add the production connector you actually use

Canva if your output is social and print, Figma if it is design files and sites. Do not add both until a project needs both.

Step 5: Add Asana or your task tool for handoff

Connect it after the planning tool, so the assistant creates tasks from an approved plan rather than from a first draft.

Step 6: Add HubSpot or Slack only with a named job

"Summarise client feedback from Slack every Friday" is a job. "Might be useful" is not. Each connector widens what the assistant can see.

Step 7: Write the stack down

Record which connectors are on, which client each is scoped to and who approved it. Storyflow connections end on their own after 30 days, so a monthly review lines up with re-signing in anyway.

A Worked Example: One Client Brief, Five Connectors, Two Days

Here is how the stack runs on a typical job. The client and every number below are illustrative: a regional coffee roaster briefing a 4-person studio on a spring campaign with 3 concept directions, 12 social assets and one 30-second video.

Monday morning: the brief arrives

The brief is a 6-page PDF the account lead drops into the client's Drive folder. In Claude, with Drive and Storyflow connected and Storyflow scoped to the coffee roaster's project, the strategist asks: "Read the spring campaign brief in the roaster's Drive folder and the brand guidelines next to it. Build a Storyflow board with the objective, the audience, the deliverables table, the budget and the open questions." The assistant reads both files through Drive and builds the board through Storyflow: groups for each brief section, a deliverables table with 12 asset rows and the video, and a list of open questions (the brief names no launch date).

Monday afternoon: three directions

Next prompt: "Add a mind map of three concept directions for this audience, each with a one-line idea, two hooks and a visual reference note." The mind map lands on the same board. The designer adds reference images to each direction by hand, and uses the upload link the assistant gives when someone tries to attach a photo in the chat.

Tuesday morning: the concept deck

"Turn the three directions into a 10-slide concept deck on this board: context, audience, three directions with two slides each, recommended direction, next steps." The deck sits next to the plan it came from. The account lead sends the client the view-only link. The client opens it with no account, and signs in to comment on direction two.

Tuesday afternoon: approval to production

The account lead asks: "What changed on the roaster board in the last day, and who changed it?" The answer lists the designer's edits; the account lead reads the client's comment on direction two on the board itself, since the connector does not read comment threads. Direction two is approved. The strategist asks Claude to create the 12 social assets and the video as tasks in Asana with owners, then asks Canva, through its connector, to create the first carousel design from the approved direction.

What the numbers look like

Nobody copied the brief into a deck by hand, and nobody exported a PDF of the concept. The client looked at the same board the team worked on, which is why the comments landed on the right slide.

Prompts You Can Copy for Client Work

These prompts assume the named connectors are on and scoped to the right client. Replace the bracketed parts.

Two habits make these prompts work. Name the client board in every prompt, so the assistant never guesses which project you mean. And ask for the output on the board, not in the chat, so the work survives the conversation.

What the Stack Costs: Solo Studio vs a 6-Person Agency

Connectors are mostly free on top of the products you already pay for. The real cost is the assistant seats and the production tools. Prices below come from each vendor's pricing page on October 9, 2026, at annual billing where offered.

How to read the table

For the solo studio, the stack that does the whole brief-to-pitch job (Claude, Storyflow, Drive, Canva Free) costs about $25 a month. For the 6-person agency, assistant seats are $120 of the $269, nearly half. Storyflow on Max is $39 for the team workspace with roles; the people you invite to boards join free, and a free account gets 25 MCP actions a week, which Storyflow's MCP page describes as enough to build a board. Team members who run heavy assistant work on the boards need their own paid plan for unlimited MCP use.

Where the money leaks

The leak is never the connector. It is the second assistant (half the team on Claude, half on ChatGPT, everyone paying for both) and the production tool bought "for AI" that nobody connects. Pick one assistant, connect the tools you already pay for, and only then buy anything new.

Which Connector for Which Agency

Agencies differ more by what they deliver than by size. Match the stack to the deliverable.

Creative and brand studio

Top picks: Storyflow and Canva. The concept, the moodboard references and the pitch deck live on a Storyflow board the client opens by link; Canva produces the finished brand assets once a direction is approved. Add Drive for the brief.

Social and content agency

Top picks: Storyflow and Canva. Plan the month of content on a board with a table of posts and dates kept in order, then produce carousels in Canva. Storyflow does not publish or schedule posts, so keep your scheduler.

Design and digital agency

Top picks: Figma and Storyflow. Figma for the design files and design-to-code; Storyflow for the brief, the site map as a diagram and the client presentation.

Video production agency

Top picks: Storyflow and Google Drive. The assistant can build shot cards and a strip board on the project board from the approved treatment; Drive holds the script and client notes. See the brief-to-production-plan guide for the full flow.

Performance or growth agency

Top picks: HubSpot and Asana. Client and deal context in every answer, and tasks created from plans. Add Storyflow when you pitch creative concepts, not for reporting.

New-business and pitch team

Top picks: Storyflow and HubSpot. HubSpot for the prospect's history, Storyflow for the pitch board and deck. The concept presentation guide covers what goes in the deck.

Freelancer or one-person studio

Top picks: Storyflow and Google Drive. Two connectors, one assistant, about $25 a month, and the client sees a board instead of an email thread.

Decision Rules

When you are not sure what to connect next, these rules settle it.

• If the deliverable is a plan, a concept or a pitch the client must see, connect Storyflow.
• If the assistant keeps asking you to paste the brief, connect Google Drive.
• If the output is a finished social or print asset, connect Canva.
• If the output is a design file or a website, connect Figma.
• If the approved plan has to become assigned tasks, connect Asana.
• If client history lives in a CRM and drafts keep missing it, connect HubSpot.
• If feedback is lost in channels, connect Slack and ask for weekly summaries.
• If a connector cannot be scoped to one client, connect it read-only or not at all.

Permissions and Client Data: The Rules to Set Before You Connect Anything

A connector is a key to a room. In an agency, the rooms belong to different clients, and some of them compete. Set these rules before the first connection.

Scope by client, not by convenience

Storyflow asks which projects the assistant may use: all, or the ones you pick. Pick the one client you are working on. It also asks whether the assistant may use documents outside projects; that option starts on when you allow all projects and off when you pick projects. Leave it off for client work.

Start read-only, then allow changes

Connect read-only for the first week on a new client. Once the team trusts the output, reconnect with changes allowed. Storyflow shows an "I trust this app" warning for apps it does not recognise, which is worth reading rather than clicking through.

Know how access ends

In Storyflow, Settings, Connected apps removes an assistant, and access ends within a minute. Every connection also ends on its own after 30 days. Personal keys, for tools that cannot run a sign-in, also last 30 days. Google Drive actions in Claude ask for approval by default, and Slack and HubSpot need admin approval before anyone connects.

Check your client contracts

Some client agreements restrict which third-party services can process their material. Read the clause before you connect a client's Drive folder or board to any assistant, and keep a written list of what is connected where.

Common Mistakes Agencies Make With AI Connectors

Mistake 1: Connecting everything on day one

Seven connectors with full access means the assistant can see seven tools' worth of every client. Add one at a time, each with a named job.

Mistake 2: Leaving the output in the chat

A brilliant concept in a chat transcript is invisible to the client and the team. Ask for the output on the board, in the deck or in the task list.

Mistake 3: One account for every client

A single Google account or workspace connected with full access is the easiest way to leak one client's plan into another client's answer. Scope per project where the tool allows it.

Mistake 4: Attaching photos in the chat and expecting them on the board

A photo attached in Claude or ChatGPT does not reach Storyflow. Ask the assistant for the upload link and drop the images there.

Mistake 5: Two assistants, two sets of permissions

Half the team on ChatGPT and half on Claude doubles the connectors to manage and the seats to pay for. Pick one default.

Mistake 6: Treating comments as approval

Neither Storyflow nor most tools here has a formal approve button. Record the approval as a note or a table row on the board with the date and who approved, so you can point to it later. A client review board keeps those notes next to the work.

Mistake 7: Forgetting connections expire

A Storyflow connection ends after 30 days. Put the re-connect in the monthly review instead of finding out mid-pitch.

When Storyflow Is Not the Right Choice

Storyflow ranks first for brief-to-board client work. It is not the answer for every agency job, and here is where to go instead.

You need formal, versioned approvals

Storyflow has comments but no approve button and no version comparison. Agencies with compliance-heavy clients need dedicated proofing software; our client feedback and approval tools guide compares the options.

You need posts published or scheduled

Storyflow does not publish or schedule social posts. Plan the content on the board and use your scheduling tool to post it.

You need a free tool today

Storyflow is paid-only during early access. Its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. If you need a free board today, Miro's free plan works with its MCP server, and Milanote's free tier holds 100 items.

You work offline or need a desktop or mobile app

Storyflow runs in the browser only. There is no desktop or mobile app and no offline mode.

Your deliverable is the design file itself

If the agency's output is a Figma file or a website build, Figma's connector does the production work and Storyflow is only the planning layer. Many design agencies are better served starting with Figma.

You need invoicing, contracts or call sheets sent and tracked

Storyflow does not do invoicing, contracts or tracked call-sheet confirmations. Use your agency management or production software for those.

A Connector Stack Template You Can Copy

Copy this into your agency's operations doc and fill it in per client. It keeps the permissions visible and the jobs named.

The first row is the one most agencies are missing. If you fill in only two rows this week, make them Storyflow and Google Drive. Agencies that want a starting board can look at the agency client project planning layout or the brief to project board page.

The Bottom Line

Agencies do not need more AI chat. They need the chat to land somewhere the client and the team can open. Connect Storyflow so Claude or ChatGPT turns the brief into a board, the board into a concept deck and the deck into a link the client opens with no account. Connect Google Drive so the assistant reads the brief instead of your summary of it. Then add Canva or Figma for production and Asana for the handoff, each scoped to one client. Start this week with your next brief: connect Storyflow to your assistant, paste the brief, and ask for the board.