CRM & Sales · Integration
eTapestry
Add eTapestry to your product for your customers, and give your AI agents governed access to it.
Embed an eTapestry integration so your customers can work their own constituent accounts, gifts, funds, appeals, and campaigns from inside your product. Every nonprofit configures its own user-defined fields and categories, so field mapping is configuration per customer rather than code, and records can be read, written back, and watched for changes so nothing drifts apart. fastn handles per-tenant authorisation and API upkeep, so onboarding another organisation is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync constituent accounts from their own eTapestry database into your product, mapped to their user-defined fields.
Write gifts and contact history back so an interaction captured in your product appears on the donor record.
Read campaigns, funds, and appeals so your product reports against the structures the team already uses.
Trigger your product when a constituent or gift record is created or updated.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a constituent's giving history before drafting a personalised follow-up.
An agent creates or updates a constituent record within governed permissions, with the action logged.
An agent reacts to a new gift and runs the next stewardship step.
Example prompt
List constituents who gave last year but have no gift this year, sorted by their previous total.
Set up eTapestry in 4 steps
- 01Open the eTapestry connector from your fastn dashboard.
- 02Have each customer authenticate their own eTapestry database.
- 03Map the constituent fields, funds, and campaigns your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the eTapestry integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an eTapestry integration without building it. Your customers connect their own eTapestry account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an eTapestry update is not your on-call problem.
- One integration serves your product and your agents. The same governed eTapestry connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
DonorPerfect
Classy
SalesforceOften used alongside
Tools the same teams tend to run next to eTapestry, across other categories.
Slack
Mailchimp
Marketo
Google AdseTapestry integration FAQ
How do I add an eTapestry integration to my product?
Enable the eTapestry connector in your fastn dashboard, then let each customer authenticate their own eTapestry account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no eTapestry client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own eTapestry account?
Yes. Every connection is scoped to the individual customer, so each authorises their own eTapestry account and only ever sees their own accounts, contacts and opportunities. 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 eTapestry 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 constituent's giving history before drafting a personalised follow-up.
Who maintains the eTapestry integration?
fastn does. When eTapestry 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 eTapestry integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual eTapestry schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from eTapestry, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in eTapestry do not drift apart.
What can I build with the eTapestry integration?
A common starting point: sync constituent accounts from their own eTapestry database into your product, mapped to their user-defined fields. 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 eTapestry integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding eTapestry does not change your per-connector cost. You can start free with 3 connected accounts.
Add eTapestry to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.