Skip to content

Keep two apps in sync, set up from your AI assistant

Describe what should be copied where. Your assistant builds an automation that checks for changed records on a schedule, updates the other app, and remembers where it stopped.

Your assistantClickRuntime connected
Create a ClickRuntime automation: every 30 minutes, copy new and changed rows from my Airtable Customers table to HubSpot contacts.
I'll look for records modified since the last run, update or create the HubSpot contact by email, and keep the last sync time.
Airtable Customers → HubSpotLive
When
Every 30 minutes
Uses
Airtable, HubSpot
RunsClickRuntime dashboard
  • 14:30✓ Airtable Customers → HubSpot · SucceededLast run14:30 · 4 synced

Can ChatGPT or Claude keep two apps in sync on a schedule?

An assistant can copy records once while you watch. Keeping two apps in sync means checking again and again and remembering what was already copied. With ClickRuntime, the assistant sets up an automation that runs on a schedule, fetches only records changed since its last run (a cursor kept in state), and creates or updates them in the other app.

Why the assistant can’t do this on its own

  • Sync is ongoing. It has to run at 3 a.m. and on weekends, not only when you ask.
  • Copying only changes needs a cursor: the time of the last sync, kept between runs. A chat starts fresh each time.
  • Both apps' keys have to be stored somewhere safe. ClickRuntime keeps them in the ClickRuntime dashboard, not in chat.

Set it up from your AI assistant

The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.

  1. 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.
  2. Step 2Paste the promptStart a new chat and paste: “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.” Change the details (times, channels, addresses) to yours.
  3. 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.
  4. Step 4Connect accounts and save keysThe assistant asks you to save an Airtable personal access token (read on that base) as AIRTABLE_TOKEN and a HubSpot private app token as HUBSPOT_TOKEN in the ClickRuntime dashboard. It can run a one-time discovery script to read the table's field names.
  5. Step 5Test itThe assistant runs a first sync limited to five records, shows what it created or updated in HubSpot, then runs the full sync and turns the schedule on.
  6. 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.
  7. Step 7Check it in the ClickRuntime dashboardEach run shows how many records changed and were synced. Runs with no changes are quick and aren't counted toward your monthly runs. State shows the cursor (the last sync time). Clearing state makes the next run resync everything.
Prompt to copy.txt

“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.”

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.

airtable_to_hubspot.pyexample
1from datetime import datetime, timezone
2from clickruntime import on_trigger, report_fetched, credentials, http, state, log
3 
4BASE, TABLE = "appXXXXXXXXXXXXXX", "Customers"
5HS = "https://api.hubapi.com/crm/v3/objects/contacts"
6 
7@on_trigger
8def run(event):
9since = state.get("cursor") or "1970-01-01T00:00:00.000Z"
10started = datetime.now(timezone.utc).isoformat()
11at = {"Authorization": "Bearer " + credentials.secret("AIRTABLE_TOKEN")}
12records, offset = [], None
13while True:
14params = {"filterByFormula": f"IS_AFTER(LAST_MODIFIED_TIME(), '{since}')", "pageSize": 100}
15if offset:
16params["offset"] = offset
17page = http.get(f"https://api.airtable.com/v0/{BASE}/{TABLE}", headers=at, params=params).json()
18records += page["records"]
19offset = page.get("offset")
20if not offset:
21break
22report_fetched(len(records))
23if not records:
24return {"summary": "Nothing changed"}
25 
26hs = {"Authorization": "Bearer " + credentials.secret("HUBSPOT_TOKEN")}
27synced = 0
28for rec in records:
29f = rec["fields"]
30email = (f.get("Email") or "").lower()
31if not email:
32continue
33props = {"email": email, "firstname": f.get("First name", ""), "lastname": f.get("Last name", ""),
34"company": f.get("Company", ""), "plan": f.get("Plan", "")}
35r = http.patch(f"{HS}/{email}", params={"idProperty": "email"}, headers=hs, json={"properties": props})
36if r.status_code == 404:
37r = http.post(HS, headers=hs, json={"properties": props})
38r.raise_for_status()
39synced += 1
40 
41state.set("cursor", started)
42log.info("Synced", {"count": synced})
43return {"synced": synced}
  • The cursor is saved only after every record succeeded, so a failed run retries the same changes next time.
  • HubSpot contacts are updated by email (idProperty=email) and created when they don't exist yet.
  • `plan` must exist as a contact property in HubSpot; the assistant checks with a discovery script first.
  • The same pattern works for Notion → Google Sheets, Sheets → Airtable or any two apps with APIs.

Trigger link and schedule

Use a schedule when the source app has no webhooks, or when a short delay is fine. Every 30 minutes is common; every 5 minutes is the shortest.

Use a trigger link when the source can call a webhook on change (Airtable automations, HubSpot workflows): each change syncs within seconds. Many setups use both, with the schedule as a safety net.

Limits

  • Runs have a time limit, so a first sync of many thousands of records is split across runs with the cursor.
  • Each app's own API rate limits apply; the http client retries rate-limited GET requests.
  • Two-way sync needs a rule for conflicts (which side wins). Tell your assistant which one.

Troubleshooting

Some records never sync.

They have no email or a field name differs. Ask your assistant to list skipped records from the last run's log.

HubSpot returns 400 property doesn't exist.

Create the property in HubSpot or ask the assistant to map it to an existing one.

I want to resync everything.

Clear the automation's state in the ClickRuntime dashboard. The next run starts from the beginning.

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.

  • Multi-step logic

    Make it two-way, with the newest change winning

    “Change my Airtable to HubSpot sync so changes in HubSpot also flow back to Airtable, and the most recently modified side wins.”
  • Trigger links

    Sync within seconds when Airtable calls a trigger link

    “Add a trigger link to my Airtable to HubSpot sync that syncs one record right away when an Airtable automation calls it, keeping the schedule as a safety net.”
  • Built-in AI

    Fill in industry from the company description with AI

    “Change my Airtable to HubSpot sync so it sets the HubSpot industry field from the Airtable company description when it's empty.”
  • Memory between runs

    Email a daily count of records synced and skipped

    “Add to my Airtable to HubSpot sync: keep a daily count of synced and skipped records and email me the totals at 18:00.”
  • Any app or API

    Also copy the records to a Google Sheet for reporting

    “Add to my Airtable to HubSpot sync: also write each synced record to my Customers report sheet, one row per customer.”
  • Multi-step logic

    Validate before syncing and flag bad rows back in Airtable

    “Change my Airtable to HubSpot sync so records with an invalid email are not synced, and their Sync status field in Airtable says why.”
  • Any app or API

    Post a Slack note when a customer changes plan

    “Add to my Airtable to HubSpot sync: when a record's Plan changes, post the customer and old and new plan to #customers in Slack.”

Can ChatGPT sync Airtable and HubSpot?

With ClickRuntime connected, yes. ChatGPT sets up a scheduled automation that copies changed records between them, keeping a cursor so only changes are copied.

How often can it sync?

Every 5 minutes at the shortest. For changes within seconds, add a trigger link the source app calls.

Does each record cost a run?

No. One run handles every changed record it finds. Runs with no changes that finish quickly aren't counted.

Which apps can it sync?

Any two apps with APIs, such as Notion, Google Sheets, Airtable, HubSpot, Salesforce or your own database's HTTPS API.

What if a run fails halfway?

The cursor only moves after a successful run, so the next run picks up the same changes. Updates by email are safe to repeat.

Other use cases

Set up your first automation in ChatGPT or Claude

Free plan. No credit card.

Server URLhttps://clickruntime.com/api/mcp