Support & Ticketing · Integration
Front
Add Front to your product for your customers, and give your AI agents governed access to it.
Front is shared email rather than a queue, and that shapes the whole integration. A conversation belongs to an inbox, and the inbox is the unit of routing, so where something lands is decided by which shared inbox it arrived in and which teammates can see that inbox, not by a queue position or a priority number. Comments are the internal layer, invisible to the customer, sitting right beside replies that are not. Drafts are their own object, so your product can compose something for a human to approve and send instead of sending it itself. Rules already move conversations around, which means a write can collide with automation a customer configured. fastn owns the per-account authorisation and the API upkeep behind it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Front account and choose which shared inboxes your product may read and write.
Create a draft for a teammate to review and send, so your product proposes the reply instead of speaking for the team.
Add an internal comment carrying the context your product holds, keeping it off the message the customer sees.
Assign a conversation or move it between inboxes, allowing for the rules a customer already has running on it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a conversation and its internal comments across only the inboxes it was given.
An agent leaves a comment or prepares a draft within scoped permissions, with the inbox it wrote to recorded.
An agent reports which conversations in a shared inbox have no assignee and how long they have sat there.
Example prompt
Which conversations in this shared inbox have nobody assigned, and which one has been waiting longest?
Set up Front in 4 steps
- 01Enable the Front connector from your fastn dashboard.
- 02Have each customer authorise their own Front account, so calls run under their credentials rather than a shared key.
- 03Decide which conversations, customers and tags your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Front integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Front integration without building it. Your customers connect their own Front account inside your product and work their conversations, customers and tags there, with no per-customer code on your side.
- Handle the part that actually costs time: support volume is spiky, and support teams notice latency immediately. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Front update is not your on-call problem.
- One integration serves your product and your agents. The same governed Front connection powers in-product features and gives AI agents scoped, audited access, so you let support work your customers' queues without leaving your product without wiring it twice.
Used by these teams
Compare with
Groove
Zendesk
IntercomOften used alongside
Tools the same teams tend to run next to Front, across other categories.
Salesforce
HubSpot
Slack
NetSuiteFront integration FAQ
How do I add a Front integration to my product?
Enable the Front connector in your fastn dashboard, then let each customer authenticate their own Front account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Front client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Front account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Front account and only ever sees their own conversations, customers and tags. 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 Front 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 reads a conversation and its internal comments across only the inboxes it was given.
Who maintains the Front integration?
fastn does. When Front 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.
Can an agent resolve a Front conversation end to end?
An agent can read the full history, post replies, change status and route within the permissions you grant it. Every action is attributed and audited, so you can show exactly what the agent did rather than inferring it.
Do I get notified the moment something changes in Front?
Yes, through event triggers rather than polling, so your product reacts to a new or escalated conversation in near real time.
What can I build with the Front integration?
A common starting point: let each customer connect their own Front account and choose which shared inboxes your product may read and write. 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 Front integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Front does not change your per-connector cost. You can start free with 3 connected accounts.
Add Front to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.