Multi-Tenancy: Working with the InAgentic.ai Platform

dogrun.ai's chatbot can now actually book appointments, not just capture leads. Extended the same calendar-checked booking flow already live for the workshop assistant into the dog-walking chat — a message like "next Saturday 2pm" gets checked against a real calendar and only confirmed if the slot is free.

The calendar being checked is a fixed identity, not a per-brand setting. Whichever site's chat triggers the check, it always looks at the same connected calendar — resolved from the admin's own login, not from which tenant's domain the booking happened on.

Getting there took two separate OAuth failures. First, Google rejected the callback outright because only a sibling feature sharing the same OAuth client had ever registered its own redirect URI — this one hadn't. After fixing that, a stale-looking "unauthorised" turned out to be a session cookie scoped to a different subdomain than the one Google was told to redirect back to.

That cookie issue is a sharp edge worth remembering. A session cookie with no explicit domain attribute is invisible across www vs. bare-domain — silently breaking any flow that round-trips through a hardcoded hostname different from wherever sign-in actually happened, not just this one.

dogrun.ai's dashboard now has a one-click "Authorise Calendar" button next to its leads table, so reconnecting the calendar doesn't require remembering a raw setup URL — a small convenience layered on top of a flow that used to only work if you knew exactly where to click.

Blog publishing for InAgentic and FileDone now goes live to their real Ghost sites instead of stopping at a draft. Confirmed along the way that even on a shared publishing code path, each tenant's Ghost instance is a genuinely separate site with its own credentials — one site's working key says nothing about whether another's does.