everydayhero

Enable the everydayhero connector in your fastn dashboard, then let each customer authenticate their own everydayhero account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no everydayhero client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own everydayhero 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.

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 campaign and donation data before answering a question about fundraising progress.

fastn does. When everydayhero 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.

Yes for reading. Fundraising pages and campaigns carry fields that differ per charity, and those are mapped per tenant rather than hard-coded.

This is a read surface. Your product reads campaign, team and fundraiser totals and the donations behind them, but the record of a gift stays where it was made. Reads are reconcilable, which is what a finance team actually needs from it.

A common starting point: connect their own everydayhero account so fundraising results appear inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding everydayhero does not change your per-connector cost. You can start free with 3 connected accounts.