Support & Ticketing · Integration
Re:amaze
Add Re:amaze to your product for your customers, and give your AI agents governed access to it.
Re:amaze is addressed per brand: the API lives on a brand-specific host under reamaze.io, so a customer with several brands has several hosts and there is no single global endpoint. Authentication is HTTP basic using a login email together with an API token, not a bearer token, which trips up clients built for the more common pattern. Conversations are identified by a slug derived from the subject rather than a numeric id, and messages are nested under that slug, so any code that assumes integer ids will fail on the first real ticket. Contacts, articles and staff are separate resources, and listings are paginated in a way that makes a full backfill noticeably slower than an incremental sync, so it is worth storing the last seen conversation and only pulling forward. fastn holds each customer's brand host and token pair and keeps them working as brands are added or credentials rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Re:amaze brand so your product reads their conversations and contacts
Create a conversation in Re:amaze when an issue is raised inside your product, with the reporter as the contact
Mirror conversation status and tags into your own dashboard so support load is visible next to product data
Attach product context to an existing conversation so agents see account state without switching tools
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a reply on a conversation but require a human to send it
Have an agent tag and route incoming conversations by topic using rules you define
Audit per tenant which conversations and contacts an agent read, keyed by brand host
Example prompt
Summarise the open Re:amaze conversations for this customer and tell me which ones are waiting on us.
Set up Re:amaze in 4 steps
- 01Enable the Re:amaze connector from your fastn dashboard.
- 02Have each customer authorise their own Re:amaze 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 Re:amaze integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Re:amaze integration without building it. Your customers connect their own Re:amaze 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 Re:amaze update is not your on-call problem.
- One integration serves your product and your agents. The same governed Re:amaze 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
Zendesk
Intercom
FrontOften used alongside
Tools the same teams tend to run next to Re:amaze, across other categories.
Salesforce
HubSpot
Slack
NetSuiteRe:amaze integration FAQ
How do I add a Re:amaze integration to my product?
Enable the Re:amaze connector in your fastn dashboard, then let each customer authenticate their own Re:amaze account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Re:amaze client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Re:amaze account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Re:amaze 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 Re:amaze integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a reply on a conversation but require a human to send it
Who maintains the Re:amaze integration?
fastn does. When Re:amaze 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 Re:amaze 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 Re:amaze?
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 Re:amaze integration?
A common starting point: let a customer connect their own Re:amaze brand so your product reads their conversations and contacts. 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 Re:amaze integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Re:amaze does not change your per-connector cost. You can start free with 3 connected accounts.
Add Re:amaze to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.