Skip to main content
Track new features, improvements, and fixes shipped to Paige.

​
August 2026

Two releases. The first was about reaching a customer after their 24-hour window had closed. The second opened the other direction — letting an outside service reach your bot — and put your media library on the API.

​
New features

  • Inbound hooks — let another service call your bot. Mint a URL under Settings → API → Inbound hooks and paste it into a payment provider, a booking tool, your CRM, or a form builder. Whenever something happens over there, it’s delivered straight to your bot to act on, exactly as it arrived. Holding the URL is the permission, so there’s nothing for the other service to sign up for; the URL is redisplayable rather than show-once, and Rotate is how you invalidate one. Each hook shows its 20 most recent arrivals so you can see whether requests are landing. Paige creates the src/routes/inbound.js handler for you and never overwrites it — and because Paige can’t vouch for who sent a request, your bot verifies the sender. See Inbound hooks.
  • Manage your media library over the API. /v1/media uploads a file, lists the project’s assets, returns a signed URL for one, and deletes one — so a catalogue sync or a connected AI agent can add images and documents the bot sends, without anyone clicking Upload. Three ways to send the file: a public URL Paige downloads, base64 bytes inline, or a normal multipart upload. Two new permissions, media:read and media:write, cover it. See Storage.
  • Connected agents can read your flows and add media. Four new agent tools: list_flows and get_flow let an agent see what a bot already does before it changes anything, and upload_media and list_media let it add a file and reference it by slug. See What a connected agent can do.
  • Send a template straight from Conversations. A Send template button now sits in the message composer. Pick an approved template, fill in its placeholders inline with a live preview, and send — the way to reach someone whose 24-hour window has closed. See Sending a template.
  • A standard conversation starter. Paige keeps a one-tap opener pinned at the top of the template picker, and offers to create it if your project doesn’t have one. Its job is to get a reply, because a reply is what reopens the 24-hour window. Sending it switches the conversation into handover so you take it from there. See The conversation starter.
  • You’re told when Meta approves a template. Approval and rejection now arrive as a toast wherever you are in the project, and the badge under Settings → Templates updates itself. A rejection shows Meta’s reason, with a View action that takes you to the template. Previously nothing told you — you had to keep reloading the page. See Template approval.
  • The Conversations Agent can propose a template. Ask it to reach someone outside the window and it puts an approved template, filled in, into an approval card — or drafts a brand-new template if none fits. It never sends or submits: your browser does that when you press the button. See the Conversations Agent.
  • Read and write your tables over the API. /v1/tables lists your project’s tables, returns a table’s columns, and reads its rows with filters, ordering, and paging — and the write side inserts, updates, and deletes rows. Two new permissions, tables:read and tables:write, cover them, and connected AI agents get the matching tools. Paige’s own platform tables stay out of reach, and every update or delete must carry a filter. See Scopes.
  • Disconnect a WhatsApp number. You can now release the number connected to a project so a different one can be connected in its place.

​
Fixes

  • The email that verifies your address no longer puts the code in the subject line, which was getting the message filtered as junk by some providers and blocking signups. The code is still in the body.
  • Filtering rows over the API with a null value is now refused rather than quietly meaning different things on different projects. Use the is operator to match nulls.
  • A table whose primary key was given a custom name no longer picks up a neighbouring table’s columns as its own, which could order a page of rows by the wrong column.
  • Messages sent through the API now appear immediately in an open conversation, instead of only after a reload.
  • When one of the AI agents fails to complete a tool call, it now tells you it failed rather than reporting success.

​
July 2026

Three releases. The middle one reorganised where your bot’s building blocks live, added Slack, and rebuilt onboarding. The last opened Paige up to the outside world with a public API.

​
New features

  • The Tools tab. Your database, storage, scheduled tasks, secrets, connectors, and logs have moved out of Settings into a tab of their own. Settings is now for configuring your project; Tools is for the machinery your bot runs on. Everything is where it was, one tab across. See the Tools tab.
  • Slack connector. Connect a Slack workspace and your bot can post to a channel — telling your team when a customer asks for a person, or when a big order lands. Sign in with Slack or paste a bot token, then pick a default channel from the dropdown. See Slack.
  • WhatsApp usernames. Claim an @handle for your business so customers can find you without knowing your number. Paige suggests handles based on your brand, shows whether Meta has reserved or approved yours, and can transfer one across from another of your numbers. See Connect your WhatsApp number.
  • SQL editor in the Database tab. Ask questions of your data that the table browser can’t answer. Read-only by default; flip the Write toggle to change data or schema. See the Database tab.
  • Saving customer media. Photos, PDFs, and voice notes customers send can now be saved to your project instead of ageing out of WhatsApp after a month. Off by default, with four modes — save nothing, save individual files by hand from Conversations, save everything, or let your bot decide. See Capturing customer media.
  • New onboarding: intro deck and a getting-started checklist. The popover tour that anchored tips to controls has been retired. New projects now open with a short six-slide intro — with walkthrough videos — covering prompting, the preview, testing on Paige Dev, connecting your number, deploying, and getting help. A checklist in the header tracks the same six steps as you complete them. Skip dismisses the intro; Replay intro brings it back. See the Quick start.
  • Workspace management moved into Settings. Create a workspace from the project-switcher dropdown, and manage it — members, permissions, invites, ownership — from Settings → Workspace inside any project that belongs to it. The project switcher now groups your projects by Personal and by workspace. See Workspaces.
  • Send a broadcast in batches. Release a big audience in waves instead of all at once: send a first batch now, watch how it lands, then release the rest yourself — all tracked as one broadcast. See Sending in batches.
  • One AI agent connection, many projects. Connect Claude, ChatGPT, or Codex once and let it work across several of your projects, each with its own permissions and its own default. You pick the projects on the consent screen, and you can add or remove projects later without reconnecting the agent from Settings → API → Connected agents. Workspace projects can now be connected too — by an owner or admin of that workspace. See Connect an AI agent.
  • Read your flows over the API. GET /v1/flows lists a project’s WhatsApp Flows and GET /v1/flows/{name} returns one with its full JSON definition, both under the Read flows permission. Until now that permission could be granted but did nothing — the API could create and update a flow, but never read one back. See Scopes.
  • A public API. Paige now has a documented REST API at /v1 — send messages, read conversations, edit files, deploy, manage flows and assemble broadcasts from your own systems. Create a key under Settings → API, choose exactly which permissions it carries, and browse every endpoint in the new API reference.
  • Webhooks, managed from the dashboard. Have Paige call your system when something happens — no code required to set it up. Create, edit, and delete webhooks under Settings → API, pick the events you care about (or name your own), and copy the signing secret, which is shown once and never again. See Webhooks.
  • Dynamic flows. A flow can now fetch live data while a customer is filling it in — the times that are genuinely free that day, their current order status, the products actually in stock. Paige stays static-first and only builds a dynamic flow when your request truly needs live data. A Dynamic badge and a live-data connection panel tell you which is which and whether the connection is healthy. See Dynamic flows.
  • Schedule a broadcast wave for later. When a broadcast is holding recipients back, you can now set the next wave to release at a time you choose instead of only sending it by hand. Pick how many and when, and Paige releases them within about 15 minutes of that time. See Sending in batches.
  • Auto-retarget quality-limit failures. Switch this on when you create a broadcast and Paige automatically tries again, about a day later, for the recipients WhatsApp blocked on quality or per-user messaging limits — the failures most likely to succeed on a second attempt. Off by default, once only, and cancellable. See Auto-retargeting quality-limit failures.

​
Improvements

  • Deploy now publishes flows that only existed in Paige. A flow you built before connecting WhatsApp is created on your number and published when you tick it in the deploy dialog, rather than needing a separate step. Per-flow failures are reported individually. See Deploy.
  • Templates the AI creates come with example values. Meta requires an example for every {{1}} placeholder; the agents now attach sensible ones automatically so a template isn’t rejected for the want of them. Give the agent real examples in your request and it’ll use those instead. See Message templates.
  • Interactive messages can carry a media header and a footer. Buttons and list menus can now open with an image and close with a line of small print.
  • “Cron Jobs” is now “Scheduled Tasks” everywhere — the same feature, named for what it does. See Scheduled Tasks.
  • Edit a database cell by double-clicking it — or tapping, on a phone. See the Database tab.
  • Pick from the tags you already use when you build a segment, with a contact count beside each one, and a warning when a tag you type matches nobody. See Segments.
  • A clearer rule about editing database rows. A table needs a primary key before its rows can be edited or deleted; older tables without one now offer an Add primary key button instead of failing quietly. See the Database tab.
  • The flow preview refreshes itself after a flow is republished, so you’re never looking at a stale copy.
  • Broadcasts appear in your per-agent credit breakdown in Settings → Usage.
  • A clearer payment-failure warning, with the 7-day deadline stated plainly and one email per failure rather than one per retry.
  • Your business profile’s industry is sent to Meta correctly — the list now maps to Meta’s own categories.

​
Fixes

  • Importing contacts no longer fails with a server error on Paige-hosted projects.
  • Resetting your preview no longer kills your live scheduled tasks.
  • New bots no longer crash on their first message.
  • Restoring a project from backup now re-enables table security, recreates sequences, and verifies the preview is reachable before reporting success.
  • Broadcast delivery updates are no longer dropped for campaigns whose name contains a colon.

​
June 2026

Broadcasts arrived — reaching many customers at once, rather than waiting for them to message you.

​
New features

  • Broadcasts. A new tab for sending an approved template to a group of your contacts. Build an audience, map your template’s placeholders to each contact’s own details, test it on up to three numbers, and schedule it. Customers who reply STOP are opted out automatically and excluded from every future broadcast. See Broadcasts.
  • Segments. Save an audience once — everyone tagged vip, everyone opted in — and reuse it on any broadcast. Segments describe who rather than freezing a list, so they stay current as your contacts change. You can also hand-pick specific people on top of the filters. See Segments.
  • The Broadcasting assistant. A chat agent on the Broadcasts tab that builds segments, drafts and submits templates, and assembles whole campaigns for you to approve. It can target people by a button they actually tapped in one of your bot’s messages — something the Segments form can’t do. It never sends anything itself. See the Broadcasting agent.
  • Import your contacts. Bring an existing customer list in from a CSV or by pasting numbers, so you can broadcast to people who haven’t messaged your bot yet. Numbers are validated, duplicates skipped. See Import contacts.
  • A safer deploy. Deploy now always syncs your table structure — new tables and columns — while copying a table’s data is a per-table choice you tick each time. Nothing is ticked by default, so a deploy can’t overwrite live customer data unless you ask it to. See Deploy.
  • Download a database table as CSV, Excel, or JSON — the whole table, or just the rows matching your current filter. See the Database tab.
  • Flows on mobile. The Flows tab is now on phones, with a swipe between your flows and the chat.
  • More than one Paige Dev number. Link a number, move it between projects, or take one over from a teammate. See Testing.

​
Improvements

  • Search a segment by name or number, not just by tag.
  • The interactive flow preview works on mobile.
  • Switching to Personal opens your most recent personal project rather than nothing.
  • You’re signed out cleanly when your session expires, instead of retrying forever.

​
May 2026

A staging-to-production release focused on smoother onboarding, trial-aware feature gating, clearer credit signals, and a richer in-app preview.

​
New features

  • Guided onboarding tour. New projects open with a contextual 7-step tour — chat, preview, Paige Dev test, connect WhatsApp, deploy, help. Each tip anchors to the relevant control and auto-advances when you complete the step. Click Skip tour to dismiss it permanently for that project. See the Quick start.
  • Open paid features during the trial. The 14-day free trial now opens the full product — Conversations, Broadcasts, Deploy, and bot runtime on your connected WhatsApp number. Gating only kicks in after the trial expires. Connecting WhatsApp through embedded signup is never gated. See Free trial.
  • Help Agent from the header. A new ? button next to Feedback in the header opens the chat sidebar straight to the free Help Agent, making in-app guidance a first-class entry point.
  • See Docs in the user menu. The account dropdown now links to the full documentation site so you can pop open the docs without leaving your current view.
  • URL buttons render in the in-app preview. Tap a cta_url button in the phone preview to open the destination inside the phone frame, with Close and Open in new tab controls. If a site blocks iframing, the preview shows an error state and keeps Open in new tab available. See Tap a URL button.
  • Try-it preview before you connect WhatsApp. The Try it, Inspect, and Debug controls in the Flows tab now work for projects that haven’t connected their own WhatsApp number yet. Paige falls back to the Paige Dev copy of the flow so you can preview straight away.
  • Try a test template on your Paige Dev tester. The Paige Dev card has a new Try now button that delivers a pre-built Meta template — with an embedded flow-trigger button — to your linked phone in one click. Rate-limited to 5 successful sends per linked number per rolling 24 hours. See Try a test template.
  • Faster signup with a warm Supabase project pool. Paige now keeps a small pool of pre-provisioned project backends ready, so new signups land in a fully working project instantly instead of waiting for provisioning.

​
Improvements

  • In-app low-credit warning and zero-balance gate. A persistent banner above the chat input warns you below one credit and stops new requests when your balance hits zero — already-streaming requests finish cleanly. The Top up button switches straight to Settings → Usage. See Low-credit warning and zero-balance gating.
  • Markdown tables in the chat sidebar. Long markdown tables emitted by the agents now scroll horizontally inside the sidebar instead of overflowing the layout.
  • Inline row editing restored in Settings → Database. Editing rows in place now sends only the columns you touched.
  • Project rename updates the project switcher. The dropdown in the header refreshes immediately after a rename.
  • Cleaner invitee onboarding. Invitees verifying their email land directly inside the workspace they were invited to, with access to the shared projects — no orphan personal project is created.

​
Fixes

  • Suspend cron now performs a backup and cleanly deletes the Supabase project, matching what the UI promises.
  • getFlowByRef falls back to matching by name when a flow name is numeric.
  • Credit balance overdraft is no longer possible without a warning.
  • The personal-number placeholder in the PaigeDev card has been replaced with the live linked number.