Connect Stripe, Shopify, and Your Calendar Into One Live View

Here’s a Tuesday-morning scene playing out right now in thousands of small businesses: Stripe open in one tab showing yesterday’s payments. Shopify in another showing orders. Google Calendar in a third showing a day that’s about to happen. Three windows into the same business, and the person running it is doing the joining — eyes flicking between tabs, holding numbers in their head, assembling the one picture no tool will draw.

This post is about ending that scene. Specifically: what it takes to get your payments, your store, and your schedule into one live view — what connecting actually involves, what it looks like when it’s done, and what questions become answerable the moment those three sources share a surface.

You can put Shopify, Stripe and your calendar on one board and read the store morning in one place.

Why these three first

Of all the connections you could make, payments + store + calendar is the highest-value starting trio, because together they cover the three questions that define a small operator’s day:

• Is money coming in? (Stripe) — the pulse. Revenue today, this week, against last. The number behind every other decision.
• Is the machine working? (Shopify) — the engine. Orders, what’s selling, what’s stalling.
• What am I committed to? (Calendar) — the cost side nobody prices. Your hours, already promised, visible next to the money they’re supposed to produce.

Any one of these alone is a widget. Two start talking to each other. All three on one surface and you have something none of their dashboards will ever be: a view of the business, not a view of a vendor’s slice of it.

What connecting actually involves

The word “integration” carries scar tissue — everyone’s lost an afternoon to one. So here’s precisely what each connection is in Vexlynk, demystified:

Stripe: a read-only key, pasted once

In your Stripe dashboard you create a restricted, read-only API key — Stripe’s own mechanism for exactly this purpose — and paste it into the source’s settings. That’s the whole ceremony. The card fills with your revenue and recent payments and keeps itself current. Read-only means structurally read-only: the connection can see money, never move it. Keys are stored encrypted and never written into your workspace.

The key takes three steps:

1. In Stripe, go to Developers → API keys and click Create restricted key. Every permission starts at None (Stripe’s guide to restricted keys).
2. Set five resources to Read: Balance, Charges, Customers, PaymentIntents and Subscriptions. Leave everything else at None.
3. Create the key, copy it (it starts with rk_live_) and paste it into the Stripe source’s settings. If you paste a full secret key (sk_) by mistake, Vexlynk asks you for a restricted key instead.

Google Calendar: an OAuth consent

Click connect, and Google’s own consent screen opens — you approve access to your calendar, pick which calendar if you have several, and you’re done. Vexlynk never sees your password; that’s the point of OAuth. The card shows your next event, today’s remaining schedule, and the days ahead. An empty week shows as an empty week — a real answer, not an error.

Two details worth knowing. The first consent is read access only; if you later add or edit an event from the calendar card, Vexlynk asks Google for that write permission separately, at that moment. And you can see or remove Vexlynk’s access at any time from your Google Account (Google’s guide to managing connected apps).

Shopify: the store connection

Same family as Stripe: an Admin API access token from a custom app on your store, read access only, and a card that shows revenue, orders waiting to ship, recent orders and top products without you visiting the admin. Shopify changed how custom apps are made this year, so here is the honest version:

1. If your store already has a custom app created in the Shopify admin before January 1, 2026, it keeps working (per Shopify). Give it exactly two Admin API scopes, read_orders and read_products (Shopify’s scope reference), install it, reveal the Admin API access token and paste it into Vexlynk with your your-store.myshopify.com domain. Shopify shows that token only once, so copy it straight away.
2. New custom apps are now created in Shopify’s Dev Dashboard and installed on the store from there (Shopify Help Center). Those apps don’t give you a token to copy from the admin. The token comes from a client-credentials exchange and expires after 24 hours, so a pasted copy would stop working the next day. Vexlynk handles that for you: in the Shopify source’s settings choose Client ID + secret, paste both values from your app’s settings in the Dev Dashboard, and Vexlynk gets and renews the 24-hour token itself. The app and the store must be in the same Shopify organization. This works in the web workspace today and arrives in the desktop app with its next update; a legacy custom app’s token still works everywhere.

One scope detail: read_orders covers orders created in the last 60 days, which is enough for a card that works in today, 7-day and 30-day windows. Stripe and Calendar take a few minutes each and need nothing technical. Shopify is just as quick with a legacy custom app and harder without one.

Worth naming what you didn’t do: no CSV exports, no Zapier flows, no spreadsheet formulas, no developer. And nothing writes back on its own — Stripe and Shopify only bring data in, and the calendar card changes an event only when you do it yourself: adding or editing saves when you click Save, and deleting asks you to confirm first.

Links checked September 28, 2026.

The view, once it exists

Now the payoff. Three cards on one canvas, arranged the way you’d arrange them on a desk — say, money on the left, store center, week on the right. What you have:

The morning glance replaces the morning tour. One look now answers what three logins used to: yesterday’s revenue, overnight orders, today’s shape. Thirty seconds, no passwords, no tabs. The checking habit doesn’t die — it gets served properly, at one counter.

The joins appear on their own. This is the part that surprises people. When revenue physically neighbors the calendar, you start seeing relationships you used to have to compute: the strong week that lines up with the launch you did; the revenue dip that matches the week you were buried in meetings and shipped nothing; the pattern that your best sales days follow your content days. Nobody runs an analysis. The layout runs it, passively, every time you look.

The data outlives the glance. Cards keep their history in view — trends, not just today’s number — so “is this normal?” gets answered by the card itself instead of by your increasingly unreliable memory of last month.

Then ask the question no dashboard could take

With the trio connected, the built-in AI agent is no longer an oracle guessing from the internet — it’s a colleague reading the same three cards you are. Which means you can ask the actual questions:

• “How does this week compare to last?” — answered from the payments card’s own data.
• “Do I have room to take on the Hendersons project?” — answered from a calendar the agent can actually see.
• “Anything unusual in the last two days?” — the cross-card sweep you used to do in your head at 7am, done on demand.

And answers can become things: ask for a summary and it lands as a note card on the canvas, next to the data it summarizes. The view assembles itself into a working surface, not just a pretty one.

Growing the view without wrecking it

Three sources is the start, not the ceiling. The expansion path that works, in rough order of payoff:

1. Attention: Google Analytics or your YouTube channel next — now marketing sits beside the money it’s supposed to make. This completes the funnel view.
2. Relationships: the CRM (HubSpot), Calendly bookings, WhatsApp — the humans behind the numbers, beside the numbers.
3. Operations: Notion databases, Trello boards — what you’re building, beside what it’s earning.

One habit keeps the canvas healthy as it grows: connect a source when you have a question for it, not because it exists. Every card should earn its place by answering something you actually check. Five well-chosen cards beat fifteen ornamental ones — and five is exactly what the free plan includes, which is not a coincidence.

The scene, rewritten

Tuesday morning, after: one workspace open. Revenue current on the left — you can see the week is tracking ahead. Two overnight orders, visible without visiting the store. The calendar card says the first call is at ten, so there’s a clear ninety minutes first. You ask the agent “anything I should know?” and get three grounded sentences instead of a tour of three tabs. Then — and this is the whole point — you start working.

The questions each pairing unlocks

The trio’s real output is the pairwise joins — each pair of sources answers questions neither could alone. Worth spelling out, because these are the queries you’ll actually run:

Stripe × Calendar: pricing your time

Revenue beside committed hours is the closest thing a service business gets to a profit-and-loss glance. The week you earned well and met little: that’s the model working. The week the calendar was packed and revenue flat: that’s the week to study, because something — free calls, underpriced work, overservicing — ate the margin. Founders who see this pairing weekly reprice within a quarter, almost universally upward.

Shopify × Stripe: the two truths about money

Orders are promises; payments are facts. Watching them side by side surfaces the gap between the two — refunds, failed payments, the lag between a busy store day and the cash landing. When the store card is loud and the payments card is quiet, you want to know that day, not at month-end reconciliation.

The lag has real numbers behind it. Stripe typically schedules your first payout 7–14 days after your first live payment. After that, money follows your payout schedule (daily, weekly or monthly) and your country’s settlement timing: with daily payouts and 3-business-day settlement, today’s payout carries payments captured three business days earlier (Stripe: Receive payouts). Shopify Payments also lets you choose daily, weekly or monthly payouts (Shopify Help Center). So a busy Friday in the store can reach your bank the next week. The payments card shows the charges and your balance long before the bank does.

Links checked September 28, 2026.

Shopify × Calendar: demand against capacity

The order spike that hits the week you’re fully booked is a fulfillment crisis you can see coming — if the two cards share a screen. This pairing is the difference between “great month” and “great month I survived.”

When a card tells you something’s wrong

Live connections occasionally break — a key expires, an authorization gets revoked, a provider has a bad hour. What matters is how failure shows up, so here’s the behavior to expect: a card that can’t refresh says so and keeps its last good data. A failed fetch never blanks a card that was working; every card carries a last-updated timestamp so you always know how fresh you’re looking at. If a card shows “Connect” instead of data, the source is installed but needs authorizing — clicking it takes you to the right settings. Thirty seconds of reconnection, not an afternoon of debugging. The design principle: a monitoring surface must never lie by omission, and stale-but-labeled beats blank-and-mysterious every time.

Two accounts, two calendars, one canvas

Real operators rarely have one of anything. Two Google accounts — personal and business — or two calendars that both matter. The model handles this the obvious way: place the source twice. Each card keeps its own configuration, so your work calendar and your personal calendar can sit side by side, each reading its own account. Same for anything else you run in duplicate. Each connection counts toward your plan’s source total, which is worth knowing when budgeting the free plan’s five — a two-calendar life uses two of them.

The one-week verdict

Give the trio seven mornings, then judge it on a single criterion: did you stop making the rounds? Not “is the canvas pretty” — did the Stripe tab, the store admin, and the calendar tab drop out of your morning ritual because one glance replaced them? If yes, you’ve recovered your first fifteen minutes a day, and the expansion path (analytics next, then the CRM) will suggest itself. If no, look at the layout before blaming the idea — nine times out of ten the cards are scattered instead of clustered, and ten minutes of arranging fixes what looks like a habit problem. The desk works when related things touch.

The tabs didn’t deserve your morning. Connect the trio free — Stripe, your store, your calendar, one canvas — and give the joining job to a surface built for it.