Data & Storage · Integration
Zendesk Sunshine
Add Zendesk Sunshine to your product for your customers, and give your AI agents governed access to it.
Sunshine is the data layer under Zendesk rather than the help desk sitting on top of it. Its purpose is to hold the things a business cares about that a ticket model has no room for, such as the order, the device, the policy or the subscription, plus the events describing what a person did and the profiles tying somebody's several identities to one customer. An embedded Sunshine integration writes custom events as they happen, reads and merges profiles, and creates and queries custom object records and the relationships between them. Two things are worth checking before you build. The custom object framework moved: the original Sunshine implementation has been wound down in favour of the native custom objects Zendesk shipped in 2023, so confirm which one a customer is on. And the schema belongs entirely to that customer, defined per account, which means reading their object types and lining them up against yours is most of the work. fastn holds each account's credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Zendesk account so the records your product holds become visible beside their conversations.
Write custom events as things happen in your product, so an agent can see what a customer did before they got in touch.
Create and query custom object records against the schema that customer defined, mapped as configuration rather than code.
Read and merge profiles so several identities for one person resolve to a single customer.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent walks a person's recent events to explain what led up to the question they asked.
An agent queries custom object records to answer something the conversation alone cannot.
An agent writes an event or a record within scoped permissions, with the object type it touched recorded.
Example prompt
What did this customer do in the week before they contacted us, and which of their records is relevant?
Set up Zendesk Sunshine in 4 steps
- 01Enable the Zendesk Sunshine connector in your fastn dashboard.
- 02Have each customer authorise their own Zendesk account, and confirm which custom object framework they are on.
- 03Read that account's object types and fields, line them up against your own model, then enable the event writes you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zendesk Sunshine integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zendesk Sunshine integration without building it. Your customers connect their own Zendesk Sunshine account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zendesk Sunshine update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zendesk Sunshine connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Airtable
QuickbaseWorks well with
ZendeskOften used alongside
Tools the same teams tend to run next to Zendesk Sunshine, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceZendesk Sunshine integration FAQ
How do I add a Zendesk Sunshine integration to my product?
Enable the Zendesk Sunshine connector in your fastn dashboard, then let each customer authenticate their own Zendesk Sunshine account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zendesk Sunshine client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zendesk Sunshine account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zendesk Sunshine account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Zendesk Sunshine integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent walks a person's recent events to explain what led up to the question they asked.
Who maintains the Zendesk Sunshine integration?
fastn does. When Zendesk Sunshine changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Zendesk Sunshine integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Zendesk Sunshine reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Zendesk Sunshine integration?
A common starting point: let each customer connect their own Zendesk account so the records your product holds become visible beside their conversations. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Zendesk Sunshine integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zendesk Sunshine does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zendesk Sunshine to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.