Automate Google Calendar + Stripe
The shared clock your workflows can read and write. Payments, subscriptions and the events behind revenue. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Meeting Follow-Through is a ready-made agent built around Google Calendar; point its last step at Stripe to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Stripe is a decision about the Google Calendar event rather than a transcription of it.
When an event starts or ends in Google Calendar…
…an agent can look up customers and charges in Stripe — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can summarise revenue activity in Stripe — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can flag anomalies in Stripe — after reading the context and deciding it should.
When a payment succeeds or fails in Stripe…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a subscription changes in Stripe…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a dispute opens in Stripe…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Stripe hand-off, setup template
Start with the google-calendar-api node and the stripe-invoice node. Configure the Google Calendar source payload, the agent input, and the Stripe operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "6946d6c9-50df-4a54-a780-f2093299d05c",
"name": "Google Calendar → Stripe",
"nodes": [
{
"id": "92a7b0bb-3c55-43b9-a322-d7d85570029e",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"calendarId": "CONFIGURE_CALENDARID"
},
"description": "Setup template for Google Calendar New Event. Listen for events created or updated on a Google Calendar and trigger the workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3c31297c-0a45-4e18-a629-5922b65fcea4",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Calendar item. Decide whether it warrants action in Stripe, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "7a2ce073-4d7e-43c6-a8b4-b64957ac9174",
"text": "Configure destination in Stripe",
"x": 512,
"y": 528,
"isEditing": false,
"type": "stripe-invoice",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"customerEmail": "CONFIGURE_CUSTOMEREMAIL",
"dueDate": "CONFIGURE_DUEDATE",
"currency": "USD",
"amount": 1,
"description": "CONFIGURE_DESCRIPTION",
"lineItems": []
},
"description": "Setup template for Stripe API. Create and send a Stripe invoice with support for single or multiple line items Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "8585a8ed-af10-4ee9-a06c-690eea9bdf0a",
"start": {
"id": "92a7b0bb-3c55-43b9-a322-d7d85570029e",
"type": "output"
},
"end": {
"id": "3c31297c-0a45-4e18-a629-5922b65fcea4",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "f1db6659-decd-46f3-a01c-4994b96ebdf6",
"start": {
"id": "3c31297c-0a45-4e18-a629-5922b65fcea4",
"type": "output"
},
"end": {
"id": "7a2ce073-4d7e-43c6-a8b4-b64957ac9174",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Calendar New Event
Listen for events created or updated on a Google Calendar and trigger the workflow.
- calendarId — Calendar ID to monitor (defaults to 'primary') Current example:
CONFIGURE_CALENDARID.
Configure Stripe API
Create and send a Stripe invoice with support for single or multiple line items
- customerEmail — Email address of the customer to bill Current example:
CONFIGURE_CUSTOMEREMAIL. - dueDate — Due date for the invoice (YYYY-MM-DD) Current example:
CONFIGURE_DUEDATE. - currency — Currency for the invoice Current example:
USD. - amount — Amount in cents for single item (e.g., 1000 for $10.00) Current example:
1. - description — Description for single item invoice Current example:
CONFIGURE_DESCRIPTION. - lineItems — Array of line items for the invoice. Each item must have 'description' and 'amount' (in cents). Example: [{"description": "Consulting", "amount": 5000, "quantity": 2}] Current example:
[].
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at Stripe, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Build it in AGNT
- Download AGNT Community Core — free and local-first.
- Connect Google Calendar with one OAuth sign-in and Stripe with an API key pasted into the vault; both land in the local vault.
- Start from a marketplace workflow, or drop google-calendar-api and stripe-invoice onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Google Calendar and what was written to Stripe.
Google Calendar and Stripe — common questions
Can I connect Google Calendar to Stripe without writing code?
Yes. Google Calendar connects with one OAuth sign-in and Stripe with an API key pasted into the vault, both from the local credential vault. You then describe the job in plain language — “when an event starts or ends, look up customers and charges” — and the agent handles the rest.
How is this different from a field-mapping Google Calendar to Stripe automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Stripe, the agent can weigh what arrived from Google Calendar, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Calendar and Stripe data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Google Calendar, Stripe, and your chosen model provider — which can be a local one.
What does a Google Calendar and Stripe run leave behind?
A receipt: what was read in Google Calendar, which tools ran with which arguments, what the agent concluded, and what it wrote to Stripe. Anything consequential can sit behind an approval gate so a person signs off before it happens.
