Marketing Automation · Integration
Thankster
Add Thankster to your product for your customers, and give your AI agents governed access to it.
Thankster turns an event in software into a real card, written in a handwriting style on real stationery and posted. That physical step is the whole design constraint for an embedded Thankster integration. A card that has been printed and put in the post cannot be recalled, edited or unsent, so the moment of commit matters far more than it does with email, and a duplicate is a second envelope on somebody's doormat rather than a second row in a database. The pieces are a template with its handwriting style and layout, the merge fields your copy leans on, a recipient with a postal address, and the campaign that decides when a card goes out, whether that is a one off, a recurring birthday or anniversary run, or a drip sequence. Each customer keeps their own account, templates and return address, and fastn holds the 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 Thankster account so cards go out on their stationery and under their return address rather than yours.
Send a card from a template when something in your product warrants a physical note, with merge fields filled from the record that triggered it.
Drive recurring runs for dates your product already stores, such as a renewal anniversary, without anyone assembling a list by hand.
Validate the recipient address before you commit, because a card in the post cannot be corrected afterwards.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts the message for a card and shows it for approval before anything is committed to print.
An agent queues a card against an approved template within scoped permissions, with the recipient it used recorded.
An agent reports which cards were sent for an account this quarter and what triggered each one.
Example prompt
Draft a thank you card for this customer's renewal and show me the wording before anything is printed.
Set up Thankster in 4 steps
- 01Enable the Thankster connector in your fastn dashboard.
- 02Have each customer authorise their own Thankster account so cards carry their stationery and return address.
- 03Map the template, merge field and recipient address fields your product uses, and decide where the approval step sits before a card is committed.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Thankster integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Thankster integration without building it. Your customers connect their own Thankster account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Thankster update is not your on-call problem.
- One integration serves your product and your agents. The same governed Thankster connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Often used alongside
Tools the same teams tend to run next to Thankster, across other categories.
Thankster integration FAQ
How do I add a Thankster integration to my product?
Enable the Thankster connector in your fastn dashboard, then let each customer authenticate their own Thankster account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Thankster client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Thankster account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Thankster account and only ever sees their own campaigns, segments and subscribers. 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 Thankster 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 drafts the message for a card and shows it for approval before anything is committed to print.
Who maintains the Thankster integration?
fastn does. When Thankster 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 I trigger a Thankster campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Thankster?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Thankster integration?
A common starting point: let each customer connect their own Thankster account so cards go out on their stationery and under their return address rather than yours. 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 Thankster integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Thankster does not change your per-connector cost. You can start free with 3 connected accounts.
Add Thankster to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.