Every 30 minutes
Turn people in your Airtable engagement table into HubSpot contacts
People added to your Airtable engagement table, such as those who comment on your LinkedIn posts, become HubSpot contacts and are marked as synced.
- Runs
- Every 30 minutes
- Apps
- Airtable, HubSpot
- AI
- Not needed
- Access
- Airtable read/write; crm.objects.contacts.write
Send this to your assistant
Create a ClickRuntime automation: every 30 minutes, take new people from my Airtable 'Engagement' table, create or update them as HubSpot contacts and mark each record as synced.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A founder posts on LinkedIn every week and the posts get comments and reactions from exactly the kind of people they want to sell to. An assistant or a scraping tool collects those people into an Airtable table, but the list never makes it into HubSpot, so sales has no idea who has been engaging.
This picks up each new person in the table and puts them into HubSpot as a contact, then writes the HubSpot ID back to the record. Engaged people become part of your sales pipeline instead of sitting in a side list.
What you get out of it
Warm prospects reach the CRM
People who already know your name are in HubSpot, where sales can follow up.
No duplicates
Contacts are matched by email, so someone who engages again updates their existing record.
Clear sync status in Airtable
Each record shows its HubSpot ID once synced, so you can see what's done.
Fits how you already collect
However people get into the Airtable table, by hand or with another tool, they flow on to HubSpot.
How it works
What happens, step by step
Every 30 minutes, ClickRuntime checks your Airtable engagement table for records without a HubSpot ID.
It sends them to HubSpot in one batch, matching existing contacts by email.
New people become contacts and existing ones are updated, with the source set to LinkedIn engagement.
Each record gets its HubSpot ID written back, so it isn't sent again.
Before it runs live
- Connect Airtable
- Connect HubSpot
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Airtable and HubSpot steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, report_fetched
BASE_ID = "appXXXXXXXXXXXXXX"
TABLE = "Engagement"
def at(method, path="", **kw):
r = http.request(method, f"https://api.airtable.com/v0/{BASE_ID}/{path}", headers={"Authorization": f"Bearer {credentials.connection('airtable', 'work')}"}, **kw)
return r.raise_for_status() or r.json()
@on_trigger
def run(event):
recs = at("GET", TABLE, params={"filterByFormula": "AND({HubSpot ID} = '', {Email} != '')", "pageSize": 100})["records"]
report_fetched(len(recs))
if not recs:
return {"synced": 0}
inputs = [{"idProperty": "email", "id": r["fields"]["Email"].lower(), "properties": {
"email": r["fields"]["Email"].lower(), "firstname": r["fields"].get("Name", ""), "company": r["fields"].get("Company", ""),
"jobtitle": r["fields"].get("Title", ""), "lead_source_detail": "LinkedIn engagement"}} for r in recs]
resp = http.post("https://api.hubapi.com/crm/v3/objects/contacts/batch/upsert", json={"inputs": inputs},
headers={"Authorization": f"Bearer {credentials.connection('hubspot', 'work')}"})
resp.raise_for_status()
ids = {c["properties"]["email"]: c["id"] for c in resp.json()["results"]}
updates = [{"id": r["id"], "fields": {"HubSpot ID": ids.get(r["fields"]["Email"].lower(), "")}} for r in recs]
for i in range(0, len(updates), 10):
at("PATCH", TABLE, json={"records": updates[i:i + 10]})
return {"synced": len(ids)}FAQ
Common questions
What fields does the Airtable table need?
Can it record where the person came from?
How does it collect people from LinkedIn?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Copy new HubSpot deals into Airtable
Every new HubSpot deal appears in your Airtable Deals table within 15 minutes, with a heads-up in Slack.
See how it worksStart an Airtable onboarding record when a HubSpot deal is won
When a deal is won, an onboarding record is created in your Airtable tracker and the contact becomes a Customer in HubSpot.
See how it worksKeep contacts in sync between Airtable and HubSpot
Contacts stay the same in Airtable and HubSpot whichever side you edit, with the most recent change winning.
See how it worksKeep exploring
Set up “Turn people in your Airtable engagement table into HubSpot contacts” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.