Third-party apps

Besides AI agents, the same OAuth door connects third-party apps that aren't AI — an automation platform, a CRM, or other software that operates your Instasent project on your behalf. You authorize each one, review what it can do, and can disconnect it at any time.

How a third-party app connects

The connection always starts from the app's side, not from inside Instasent. When the app sends you to Instasent to authorize it, you get an OAuth consent screen where you sign in, choose the project (or projects), review the permissions the app is asking for, and approve.

A third-party integration of this kind is an API integration: its consent shows the requested permissions as a list you can trim before approving, and the permissions it can hold include ones that write — create or change things — not just read. You decide which ones to grant.

What it's not

• It's not bringing data into Instasent. An integration that feeds contacts or events into your audience — a Shopify or Klaviyo connector, a webhook — is a data source, not a connected app. A connected app operates your project from the outside; a data source moves data into it.
• It's not the AI assistant built into Instasent. That's part of the product itself — you don't connect anything to use it.
• It's not your own AI. An assistant connects through the same OAuth door, but as an MCP client working with a curated set of tools, and it approves its permissions as a package. A third-party app here is a classic API integration: it reaches the full API, and its permissions are a list you can trim.

Managing and revoking

Every third-party app you connect appears alongside your other connections in Connected apps, where you can see its permissions and projects, change which projects it reaches, and disconnect it. How much of your data it actually receives, whatever it was granted, is Data access.

Are you the one building the app?

Everything above is written for the person installing an app somebody else built. If you are on the other side — you are building software that your own customers will connect to their Instasent projects — you want the developer documentation instead, because what you need is the authorization contract, not the consent screen.