Introduction

Raindrop, and the integrations that follow it, all work the same way. You hold the account with the provider, you give OnCore an API key to it on the tenant whose calls you want delivered, and each of that tenant's calls is delivered into your own workspace there as it finishes.

What it is#

An integration is a connection between one OnCore tenant and a third-party product you have signed up for yourself. One key covers the tenant you connect it in, and every assistant in that tenant is included, including assistants you create later. Create an API key in your account with that provider, paste it into OnCore, and delivery starts from your next completed call.

Everything downstream of that stays with the provider: the workspace the calls land in, whatever that product does with them, and the bill.

What's available#

• Raindrop (raindrop.ai): monitoring and observability for AI agents. Every completed call arrives in your Raindrop workspace within seconds of the caller hanging up, where you describe the behaviours you care about in plain English and Raindrop finds them across all of your calls.

What gets sent#

Every integration page states exactly what leaves the platform, and it is worth reading that section before you connect one.

For Raindrop a completed call arrives as one event, carrying the transcript as a labelled script and the call's metadata: the caller's number, the number they dialled, which assistant answered, the models it ran on, how long the call lasted and the reason it ended. Any tools your assistant used appear where it used them. Events are attributed to the assistant that answered, so Raindrop's per-user views and alert thresholds count your assistants rather than your callers. Audio recordings and the call summary are not sent.

The transcript is the conversation verbatim, so anything a caller says out loud is in it, alongside their number. A workspace receiving your calls holds the same personal data your call records do, and deserves the same access controls and retention policy.

Bring your own account#

You sign up with the provider directly, at their pricing, on whatever plan suits your volume, and your usage is billed to you by them rather than by OnCore. OnCore stores the key you paste in and delivers your calls to your workspace.

That is the whole commercial arrangement, and it is the point rather than a caveat. The data lands in an account you control, so what happens to it after it arrives is governed by your agreement with the provider.

How to set it up#

In the OnCore dashboard, open Platform, then Integrations, then the integration you want. Paste the key from your account with that provider and save. OnCore checks the key with the provider before storing it, so a key that was mistyped or already revoked is refused at that moment rather than failing quietly later.

The key you paste applies to the tenant you are working in. Every assistant in that tenant starts delivering from that moment, including assistants you create later, so a customer with several tenants connects each one.

Each integration has its own page with the walkthrough, what it sends, and what to expect once it is live. Start with Raindrop.

Limits & FAQ#

• Only completed calls are sent. Nothing is delivered while a call is still in progress.
• Delivery starts when you connect. Calls that finished before that are not sent afterwards, and there is no backfill.
• The connection covers the tenant you connect it in. There is no per-assistant setting, so every assistant in that tenant has its completed calls delivered, including assistants you create later. Other tenants are unaffected.

Do we buy this from OnCore? No. You hold the account with the provider, at their pricing, and your usage is billed by them.

What happens if we rotate or revoke the key? The old key stops working for OnCore at the same moment, and nothing in OnCore flags it. Paste the current key in and use the connection test on the integration's screen to confirm it is accepted. Delivery resumes from the next completed call rather than from the gap.

We have several tenants. Do we connect each one? Yes. The key is stored per tenant, so connect the tenants whose calls should be delivered and leave the others alone.

What happens to our data if we disconnect? Delivery stops for that tenant. Everything already in your workspace with the provider stays there, under your own account with them, so disconnecting in OnCore deletes nothing.

How do we know it is working? Place a call and watch it arrive. A completed call reaches your workspace within seconds of the caller hanging up.

Next steps#

• Raindrop: connect your Raindrop workspace and see what lands in it.
• Recording & transcripts: the written record of every call, inside OnCore.
• Read call activity: pull the same calls over the REST API.