MCP Builder
Build with your AI agent. Run automatically in the cloud.
Connect Claude Code, Cursor, or Codex through MCP. Describe the work once; events in your apps start the saved workflow in Latenode, even after you close your agent.
Cursor
CodexYour agent builds it. You connect your apps, test, and activate. Latenode handles the cloud execution, with every step visible and editable.
Claude CodeLatenode connectedBuild a Latenode workflow: new HubSpot contact → research and qualify → update the CRM → save a Gmail draft.
Done. The workflow is in Latenode.
Five connected steps. Kept inactive for your review.
Your workspaceDescribe it in Claude Code. Open and edit it in Latenode.
Cloud execution
Close Claude Code. Your workflow keeps going.
Once you connect, test, and activate it, new app events run your workflow in Latenode’s cloud.
Claude Code
Session closedWorkflow already built.
Your agent’s job is done.
You don’t need to keep your computer or chat session running.
Active in cloud
HubSpot · New Contact
Alex Morgan · northstar.example
- Research companyLatenodeComplete
- Qualify leadLatenodeComplete
- Update ContactHubSpotComplete
- Create DraftGmailComplete
CRM updated. Draft ready for your review.
No server to deploy. No webhook handler to maintain.
Triggers use instant events or polling, depending on the app and event.
What will you build?
Which task would you like to hand off?
Every example starts with a real app event. Pick one to see the steps, result, and prompt.
Give every new lead a researched first response.
Sales gets company context, a qualification reason, and a draft it can review.
HubSpot · New Contact
A new CRM contact provides the email and company domain.
Result · Updated CRM contact + Gmail draft
GmailDraft · not sentA simpler way to automate customer reports
Hi Alex, I noticed Northstar builds software for growing teams. Would it be useful to explore automating customer reports across your apps?
Company research, fit assessment, and a personalized first email, ready for human review.
Cloud workflowHubSpot · New Contact → Latenode · Research company → Latenode · Qualify lead → HubSpot · Update Contact → Gmail · Create Draft
Ask Claude Code
Claude CodeWhen a contact is created in HubSpot, research the company, qualify the lead, update the contact, and save an introductory email as a Gmail draft. Do not send emails. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Answer with the customer’s context already in hand.
Skip the CRM search before every reply. Review a draft informed by the customer record.
Gmail · New Email
Sender, subject, message, and conversation reference.
Result · Gmail reply draft
GmailReply draftRe: Connecting our reporting tools
A reply informed by your CRM
Hi Alex, thanks for reaching out. Based on your team’s reporting setup, we can start with the CRM data you already use and map the next steps together.
A contextual reply saved in the conversation for your team to review and send.
Cloud workflowGmail · New Email → HubSpot · Find Contact → Latenode · Prepare reply → Gmail · Create Draft Reply
Ask Claude Code
Claude CodeWhen a new email arrives in Gmail, find the contact in HubSpot and prepare a reply using their CRM context. Save it as a Gmail draft reply. Do not send emails. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Keep the team up to date as new data arrives.
Turn a fresh spreadsheet row into checked figures and a useful team update.
Google Sheets · New Row Added
A new sales row in the spreadsheet you choose.
Result · Slack team update
Slack#sales-updatesPipeline update
West region report updated
The new entry passed validation. Regional totals have been recalculated, and the latest figures are ready in the team’s reporting sheet.
Checked sales figures and a link to the source row, delivered to the right channel.
Cloud workflowGoogle Sheets · New Row Added → Latenode · Validate fields → Latenode · Calculate figures → Slack · Team update
Ask Claude Code
Claude CodeWhen a new row is added in Google Sheets, validate its fields, calculate the key figures, and post an update to Slack. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Turn incoming files into checked records.
Extract invoice details once and flag missing values before they reach finance.
Google Drive · New or Modified File
An invoice in the connected folder, selected in the trigger settings.
Result · Spreadsheet record + exception notification
Google SheetsDocument registerSource: supplier-invoice.pdf
Document fields saved
Supplier, invoice date, total, and reference were extracted and checked. The source file stays linked to the record.
Validated invoice fields, with a notification when a required value needs review.
Cloud workflowGoogle Drive · New or Modified File → Latenode · Extract fields → Latenode · Validate values → Google Sheets · Save record → Slack · Flag exceptions
Ask Claude Code
Claude CodeWhen a file is added or changed in our invoices folder in Google Drive, extract and validate its fields, record them in Sheets, and flag exceptions in Slack. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Put the context next to the payment alert.
Give the team the customer, invoice, and next action in the same notification.
Stripe · New Events
Filter the event stream for the failed-payment event your process uses.
Result · Slack payment alert
Slack#billing-alertsPayment follow-up
Invoice needs attention
A payment failed for Northstar. Customer and invoice details are attached so the billing team can decide the next step.
Customer, invoice context, and a record link, ready for follow-up.
Cloud workflowStripe · New Events → Latenode · Filter failed payment → Stripe · Get invoice context → Slack · Notify team
Ask Claude Code
Claude CodeUse Stripe New Events to receive app events, filter for failed payments, look up the invoice context, and notify our team in Slack. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Move a new brief toward a reviewable post.
Connect research, writing, and image generation to the place your team plans content.
Notion · New Page in Database
A new content brief in the selected database.
Result · Telegram review message
TelegramEditorial reviewContent package ready
Your CRM automation post
A researched draft and a generated image are ready for review. The original brief is linked so the editor can check the angle and sources.
A post and image together, ready for an editor to check.
Cloud workflowNotion · New Page in Database → Latenode · Research brief → Latenode · Write post → Latenode · Generate image → Telegram · Send for review
Ask Claude Code
Claude CodeWhen a page is created in our Notion briefs database, research the topic, write a post, generate an image, and send both to Telegram for review. Do not publish automatically. Build this in Latenode. Ask me for the app connections, rules, and destinations. Keep the workflow inactive so I can inspect and test it first.
Start with a task from your own team.
Lower repeat costs
Let Claude build it. Let Latenode repeat it.
Move repeatable decisions and formatting into a saved workflow. Keep model calls for the work that needs AI.
10,000 · New HubSpot contacts / month
Claude: $90.00 / month · API usage
HubSpot · New Contact → Model call · Choose route → Model call · Write message → Slack · Send message
Latenode: $4.80 / month · CPU runtime
HubSpot · New Contact → Saved logic · Routing rule → Saved logic · Fill template → Slack · Send message
Same routing task. Two alternative ways to run it.
$85.20 saved per month in this example.
Research, qualification, and original writing still use AI tokens when your workflow calls a model. This example only replaces routing rules and template formatting.
How this estimate works
Claude Sonnet 5: two calls per contact, totaling 2,000 input + 500 output tokens. Standard API rates: $2 / 1M input and $10 / 1M output tokens. No caching or batch discounts.
Latenode: 5 CPU seconds per complete run. Uses progressive CPU-second pricing, assuming the 10,000 free monthly CPU seconds are still available.
These are assumed workloads, not a measured benchmark or a comparison of Claude Code subscription plans. Initial building, third-party app fees, external hosting, and taxes are excluded. Actual usage varies.
Pricing sources: Claude API · Latenode. Rates checked Sep 11, 2026.
Choose how it works
Same trigger. Same goal. Your choice of logic.
Keep a known sequence, or let a cloud agent adapt its research to each lead.
Lead qualificationCloud workflowFollow the steps you designed.
HubSpot New Contact → research company → qualify lead → update HubSpot contact → create Gmail draft. AI works at defined steps; the workflow controls their order.
- HubSpot · New Contact
- AI step · Research company
- AI step · Qualify lead
- HubSpot · Update Contact
- Gmail · Create Draft
Every new contact passes through the same sequence.
Choose from the tools you allowed.
HubSpot New Contact → Latenode AI Agent → update HubSpot contact → create Gmail draft. Company research and CRM context branch from the agent as callable tools, not sequential steps.
- HubSpot · New Contact
- Latenode · AI Agent
- HubSpot · Update Contact
- Gmail · Create Draft
Tools you configure
- Latenode · Company research
- HubSpot · CRM context
The agent can use company research and CRM context when needed.
Built with Claude CodeRuns in the cloudYour apps, connected by the data
The right data. In every step.
Your agent connects contact details, company research, and qualification to the right CRM fields and a personalized email draft.
Contact 1042 · data mappingMapped by Claude CodeHubSpot New Contact provides a contact ID, email, and company domain. Research adds industry, team size, headquarters, product, and sources. Qualification adds fit, reasons, and an outreach angle. Claude Code maps these outputs to the same HubSpot contact and a Gmail draft.
- HubSpot · New Contact
- Latenode · Research company
- Latenode · Qualify lead
- HubSpot · Update Contact
- Gmail · Create Draft
Available data
1New Contact
- Contact ID
- 1042
- [email protected]
- Company domain
- northstar.example
2Company research
- Industry
- B2B software
- Team size
- 50–200 employees
- Headquarters
- London, United Kingdom
- Product
- Customer analytics and reporting
Research sources
- Company & team
- northstar.example/about
- Product & use case
- northstar.example/product
3Lead qualification
High fit · 2 of 2 criteria matched
- Why this lead
- B2B software business with 50–200 employees. Matches your target industry and team-size criteria.
- Suggested outreach angle
- Automate customer reporting across the CRM and other apps.
Update Contact
- Contact ID
- 1Contact ID
- Company profile
- 2Industry2Team size2Headquarters2Product
- Research references
- 2Research sources
- Lead qualification
- 3Fit assessment3Qualification reason
- Outreach notes
- 3Outreach angle
Contact 1042 · High fit
Northstar · B2B software · 50–200 employees · London. Company profile, source references, qualification reason, and suggested outreach angle saved to the same contact.
Ready for your sales teamCreate Draft
- To
- 1Email
- Company context
- 2Industry2Product
- Personalization context
- 3Qualification reason3Outreach angle
A simpler reporting workflow for Northstar
Hi Alex, I saw Northstar builds customer analytics software for B2B teams. We help teams like yours automate customer reporting between their CRM and other apps. Would it be useful to compare notes on your current process? Best, Jordan
Saved in Gmail for your review · not sentStart with the event your team already works from.
Need custom logic?
JavaScriptHTTPAdd JavaScript for a custom format or HTTP to connect another API.
Visual control
See the workflow. Change it by hand or by prompt.
Open a node to inspect its condition, destination, or field mapping. Change it yourself, or ask Claude Code to update it.
Your team can follow the routing without reading generated code. Test changes in development while the published workflow keeps running.
Route new HubSpot contacts with a high fit assessment to our priority sales queue. Keep the remaining contacts in the standard queue.
get_scenarioupdate_scenarioHubSpot New Contact → Qualify lead → Standard queue
Rule configuration
- Field
- Lead fit
- Match
- High fit
- Destination
- Priority queue
Cloud run history
Follow an app event through every step.
See what started a run, what each node received, and what it produced. The event, logs, and results stay together in Latenode’s cloud.
Open a run to inspect the data yourself, or ask your agent to help investigate it. Here, one new HubSpot contact becomes a qualified CRM record and a Gmail draft.
Show me the cloud run for the new HubSpot contact and the draft it created.
Gmail · Draft previewA simpler way to automate customer reports
Hi Alex, I noticed Northstar builds software for growing teams. Would it be useful to explore automating customer reports across your apps?
Execution history
Newest first- 10:42 · Contact 1042SuccessSelected run
- 10:35 · Contact 1041Success
- 10:21 · Contact 1040Success
Contact 1042 · Step data
- Incoming event
- HubSpot New Contact · contact_id: 1042 · [email protected]
- Qualification
- High fit · B2B software company, 50–200 employees; matches the configured criteria.
- Result
- HubSpot contact updated · Gmail draft saved · No email sent
Connect your agent
Connect your agent and start building.
Choose your client below and connect it to Latenode with MCP. Add the recommended builder skill, then describe your first workflow.
Connection guide with four steps: create a token, configure your MCP client, install the recommended builder skill, and send a first workflow request.
Create a Latenode token
Open the MCP page in your Latenode account. Create a token, choose its name and expiry, and copy it when it appears.
Open Latenode MCPConnect your client
Replace YOUR_TOKEN_HERE in the command or configuration with your Latenode token before using it.
Claude Code
Run this command in your terminal. It makes the Latenode server available across your projects.
claude mcp add --transport http --scope user latenode https://platform-mcp.latenode.com/api/v1/mcp --header "Authorization: Bearer YOUR_TOKEN_HERE"In Claude Code, run /mcp to check the server status.
Cursor
Create or open ~/.cursor/mcp.json. Add the latenode entry under mcpServers and keep any existing server entries.
{ "mcpServers": { "latenode": { "url": "https://platform-mcp.latenode.com/api/v1/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN_HERE" } } } }Save the file, then return to Cursor.
Other agents
Add an HTTP MCP server in your client’s settings using this URL and header. Follow your client’s configuration format.
https://platform-mcp.latenode.com/api/v1/mcpFind instructions for your clientAuthorization: Bearer YOUR_TOKEN_HEREAdd the recommended builder skill
Run this from your project folder and follow the installer prompts. The skill adds Latenode’s scenario-building instructions for supported coding agents, including Claude Code and Cursor.
npx skills add latenode-com/skills --skill latenode-scenario-builderAsk for your first workflow
Paste this into your connected agent, or replace it with a task from your team.
Build a Latenode workflow triggered by a new contact in HubSpot. Research the company, qualify the lead against my criteria, update the contact, and save a personalized introductory email as a Gmail draft. Ask me for the app connections, qualification criteria, and CRM fields to update. Keep the workflow inactive so I can inspect and test it first. Create drafts only; do not send emails.Connect HubSpot and Gmail in Latenode. Check the trigger, qualification criteria, and field mappings, then test the workflow. Activate it when you’re ready: new HubSpot contacts will start cloud runs, even after you close your agent.