Send new leads to HubSpot automatically, set up from your AI assistant
Your assistant builds an automation that receives each lead from your form, creates or updates the HubSpot contact, adds a note with the message, and tells sales in Slack when it's worth a call.
- When
- Each incoming event
- Uses
- HubSpot, Website form
- 09:03✓ Website leads → HubSpot · SucceededLast run09:03 · contact updated
Can ChatGPT or Claude add new leads to HubSpot automatically?
An assistant can create a HubSpot contact while you're chatting, but it can't catch leads as they arrive at 2 a.m. With ClickRuntime, the assistant sets up an automation with a trigger link for your form. Each lead creates or updates the HubSpot contact by email, with the message added as a note, without anyone opening a chat.
Why the assistant can’t do this on its own
- Leads arrive when you aren't chatting. Something has to be listening at a URL all the time.
- Your HubSpot key has to live somewhere safe. ClickRuntime keeps it as a secret in the ClickRuntime dashboard, and the chat never sees it.
- Duplicates need a lookup first. The script searches HubSpot by email before creating anything, which a one-off chat message can't guarantee every time.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysThe assistant asks you to create a HubSpot private app with the contacts and notes scopes and save its token as HUBSPOT_TOKEN in the ClickRuntime dashboard. It gives you the trigger link to set as your form's webhook URL, plus a shared secret so the link only accepts your form.
- Step 5Test itThe assistant sends a test lead to the trigger link with an address like test+lead@yourcompany.com, then checks HubSpot shows the contact with the note. You can delete the test contact afterwards.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardEach lead appears as an incoming event with the run that handled it and its result, such as “created 123456” or “updated 123456”. Failed runs keep the event, so after a fix you replay the lead instead of losing it.
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- The trigger link checks a shared HMAC secret before the script runs, so `event.is_verified` is true only for your form.
- Search by email first, then update or create: one contact per person, however many times they fill in the form.
- HubSpot's v3 CRM API is called directly over HTTPS; no extra package is needed.
Trigger link, not a schedule
Use the trigger link when your form or website can send a webhook. Leads reach HubSpot in seconds.
If leads land somewhere without webhooks (a shared inbox or a spreadsheet), use a schedule that checks every 15 minutes and remembers the last lead it handled.
Limits
- Each lead is one run.
- HubSpot private app tokens are limited to the scopes you give them; add the notes scope or the note step fails with 403.
- HubSpot's own API rate limits apply; a single lead uses three or four calls.
Troubleshooting
Runs fail with 401 from HubSpot.
The token was rotated or mistyped. Save the new one as HUBSPOT_TOKEN in the ClickRuntime dashboard and replay the failed events.
Notes don't show on the contact.
The association is missing or the token lacks the notes scope. Ask your assistant to check the run log; it compares the call with HubSpot's API docs.
Every event is skipped as not verified.
The form isn't sending the signature header the trigger link expects. Ask the assistant to show the trigger link's signature settings and match them in your form tool.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Built-in AI
Score each lead against your ideal customer and set a HubSpot property
“Change my website leads to HubSpot automation so it scores each lead 1 to 10 against our ideal customer (B2B SaaS, 20–200 staff) and saves the score on the contact.”
- Any app or API
Alert #sales in Slack for leads scoring 8 or more
“Add to my website leads to HubSpot automation: when a lead's score is 8 or more, post the name, company and message to #sales in Slack.”
- Built-in AI
Summarise long messages into a one-line note title
“Change my website leads to HubSpot automation so the note starts with a one-line summary of the message, followed by the full text.”
- Multi-step logic
Assign the contact owner by country or company size
“Change my website leads to HubSpot automation so it sets the contact owner to Maya for UK leads and to Sam for everyone else.”
- Memory between runs
Count leads per day and email you if a day has none
“Add to my website leads to HubSpot automation: count leads per day, and email me at 18:00 if no lead arrived that day, in case the form broke.”
- Schedules
A Monday summary of last week's leads by source
“Add to my website leads to HubSpot automation: every Monday at 8, email me how many leads came in last week and from which pages.”
- Any app or API
Send each new lead a welcome email through your email service
“Add to my website leads to HubSpot automation: send new contacts a welcome email through Resend from hello@ourcompany.com.”
Questions about form leads to your crm
Can ChatGPT add leads to HubSpot automatically?
With ClickRuntime connected, yes. ChatGPT sets up an automation with a trigger link; your form sends each lead there and the script creates or updates the HubSpot contact.
Will it create duplicate contacts?
No. The script searches HubSpot by email first and updates the existing contact when there is one. Repeated deliveries of the same event are skipped.
Does it work with Salesforce or Pipedrive?
Yes. Ask for that CRM instead; the assistant uses its API with a key or OAuth connection you add in the ClickRuntime dashboard.
Where does the HubSpot token go?
Into the ClickRuntime dashboard as a secret. It never goes into the chat and is masked in logs.
Can it qualify leads with AI?
Yes. The built-in AI can score or label each lead, no API key needed, including on the free plan. See the Extend it list.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.