An all-in-one platform still has to live in a world with an accounting package, a mail tenant and an RMM. Every connector here is a first-class part of Tantivo with its own connection handling, sync and webhook verification — not a webhook recipe you maintain.
Connect via Intuit OAuth and export customers and invoices from Tantivo to QuickBooks, operator-driven so nothing syncs behind your back. Mapping between Tantivo clients and QuickBooks customers is explicit and reviewable.
Stripe Connect lets you take card and ACH payments against a Tantivo invoice through a hosted pay link. Money events reconcile back onto the invoice ledger; tax settings are yours to enable.
Connect a shared mailbox and inbound mail becomes tickets — replies thread onto the existing ticket, and operator replies send back out from the same mailbox. Unmatched mail lands in a triage queue rather than vanishing.
Sign in with Microsoft on both the operator app and the client portal, with a strict verified-email match — an account only signs in if its verified address maps to an existing invited user.
Pull managed devices into the Tantivo asset inventory so the machines you monitor and the assets you bill for are the same list.
Connect with an API key and push audience segments built from your CRM data into Mailchimp audiences.
Search for lookalike prospects modelled on a customer you already have, and bring the results in as leads with their source recorded.
Pull survey responses in so client satisfaction sits next to the tickets and contracts it relates to.
Feed the AI-curated newsletter from RSS sources and the GDELT news index, so the weekly send is drafted from real industry news rather than invented.
Send SMS alerts for urgent ticket events to on-call staff, with delivery webhooks verified before anything is written.
Deliver invoices and platform email from your own verified sending domain, with DNS records surfaced in the app and verification checked before the first send.
Every drafting, triage and summarisation feature calls Claude through a single audited gateway that records the model, provider and token cost of each call.
Document embeddings for semantic search over your knowledge base. There is deliberately no fallback embedding model — vectors from two models are not comparable, so a misconfiguration fails loudly instead of poisoning the index.
Every connector has a manage page in Settings. You authorise it — OAuth where the vendor supports it, an API key where they do not — and the credential goes straight into the per-tenant vault. The connection row holds a reference, never the secret.
OAuth state is bound to the principal who started the flow, so a callback cannot be replayed by anyone else. Inbound webhooks are signature-verified before a single row is written, and a replayed webhook is recognised rather than processed twice.
Disconnecting is one action and it destroys the stored credential. There is no lingering token you have to remember to revoke at the other end.
Not yet. Connectors today are built into the platform rather than assembled by you from an API. A documented public API is a real gap we would rather name than pretend around — if it is a requirement for you, say so and it will weigh on the roadmap.
Possibly. Connectors follow a fixed internal shape, so adding one is well-trodden work rather than an adventure. Email support@tantivo.ai with the tool and what you need to move in or out of it.
In the per-tenant vault, envelope-encrypted, with the key-encrypting key held in Azure Key Vault — never as a column on a connection row. Disconnecting a connector destroys the stored credential. Every read is audited.
The QuickBooks export is operator-driven by design — you decide what goes across and when. Inbound flows like ticket email and RMM device sync run on a schedule once you connect them, which is the point of connecting them.
Bring acquisition, delivery and billing into one transparent, AI-native system. Join the waitlist for the private trial.
Prefer email? support@tantivo.ai