Turn Figma launch assets into channel-specific briefs | Copy-Paste AI Recipe

Name: Turn Figma launch assets into channel-specific briefs
Prep time: 16 min
Ingredients: HubSpot AI system; Gmail AI system

NextFlows Contributors

doi:nextflows.ai/recipes/turn-figma-launch-assets-into-channel-specific-briefs-marketing-38

⚡ TL;DR

✓ Publish faster by converting approved notes into ready-to-edit social, email, and content drafts for your team
✓ 16 minutes to first success
✓ Review before sending
✓ Uses HubSpot MCP, Gmail MCP

Before you start

0/4

Claude Desktop installedHubSpot MCP access configuredGmail MCP access configuredPermission for HubSpot read access, Gmail read access, Draft or comment permission with human review

Setup (16 min)

0/5

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

2Connect Gmail MCP so the assistant can combine context.

3Grant the minimum read scopes needed for this ads 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: Turn Figma launch assets into channel-specific briefs.
Use the connected HubSpot MCP, Gmail MCP tools to gather only the information needed for ads.
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: HubSpot MCP, Gmail MCP.

Expected outcome

Publish faster by converting approved notes into ready-to-edit social, email, and content drafts for your team

Success checklist

0/4

The output explains the ads 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 HubSpot 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.