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.
- When
- Every 30 minutes
- Uses
- Airtable, HubSpot
- 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.
- 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: 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.
- 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 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.
- 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.
- 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 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.
“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.
- 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.”
Questions about sync data between apps
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
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 →Form leads to your CRM
“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.”
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 →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.