Draft customer story angles from CRM activity notes | Copy-Paste AI Recipe

Name: Draft customer story angles from CRM activity notes
Prep time: 7 min
Ingredients: Figma AI system; Notion AI system

NextFlows Contributors

doi:nextflows.ai/recipes/draft-customer-story-angles-from-crm-activity-notes

⚡ TL;DR

✓ Save 2 hours weekly by turning scattered marketing updates into a clear action list for the next campaign review
✓ 7 minutes to first success
✓ Read-only
✓ Uses Figma MCP, Notion MCP

Before you start

0/4

Claude Desktop installedFigma MCP access configuredNotion MCP access configuredPermission for Figma read access, Notion read access

Setup (7 min)

0/5

1Connect Figma MCP in your MCP client and confirm the server shows as available.

2Connect Notion MCP so the assistant can combine context.

3Grant the minimum read scopes needed for this email workflow.

4Open the workspace, channel, repository, database, or account you want the assistant to use.

5Paste the prompt from this recipe into your AI client.

The prompt

You are helping a Marketing teammate with this workflow: Draft customer story angles from CRM activity notes.
Use the connected Figma MCP, Notion MCP tools to gather only the information needed for email.
Create a concise result with: summary, important details, recommended next actions, owners, and links to sources.
Flag anything uncertain, stale, sensitive, or missing instead of guessing.
Do not make changes without asking me to confirm the final draft.

Paste into Claude Desktop. It will use your connected AI servers: Figma MCP, Notion MCP.

Expected outcome

Save 2 hours weekly by turning scattered marketing updates into a clear action list for the next campaign review

Success checklist

0/4

The output explains the email context in plain English.Every recommendation includes a source, owner, or next action.Sensitive data is summarized only at the level needed for the task.Marketing teammates can use the result without asking for extra background.

Troubleshooting

MCP server is not available in the client

Cause

The server config was not saved, the client was not restarted, or Node.js cannot run npx.

Solution

Run Figma MCP manually with its install command, then restart your MCP client.

The assistant cannot find the expected records

Cause

The connected account lacks access to the workspace, channel, repo, database, or page.

Solution

Grant the missing read scope and test with one known record before running the full recipe.

The result is too broad or includes stale context

Cause

The prompt did not limit the date range, source, account, or project clearly enough.

Solution

Add the relevant team, date range, channel, repo, account, or page name to the prompt.