Commerce & Payments · Integration
Ecologi
Add Ecologi to your product for your customers, and give your AI agents governed access to it.
Embed an Ecologi integration so your customers can trigger climate contributions from events in your product and read their own impact records back, each using their own Ecologi account. Requests are deduplicated per event, so a retry after a timeout does not submit the same contribution twice, and every call is logged per tenant so an impact record can be traced back to the event that created it. fastn handles each customer's credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers link their own Ecologi account so contributions come from their subscription, not yours.
Trigger a contribution when a defined event happens in your product, without bespoke code per customer.
Read impact records back so your product can show a customer their own totals in context.
Keep a per-tenant log of what was triggered and when, so any figure shown can be traced.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a customer's impact records before answering a question about their totals.
An agent triggers a contribution within governed permissions, with the action audited.
An agent reacts to a completed contribution and updates the customer-facing summary.
Example prompt
Show this customer's contributions from the last quarter and which product events triggered them.
Set up Ecologi in 4 steps
- 01Open the Ecologi connector from your fastn dashboard.
- 02Have each customer authenticate their own Ecologi account.
- 03Map the product events that trigger a contribution and the fields you read back, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Ecologi integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Ecologi integration without building it. Your customers connect their own Ecologi account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Ecologi update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ecologi connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
StripeWorks well with
SlackOften used alongside
Tools the same teams tend to run next to Ecologi, across other categories.
NetSuite
Notion
Box
DocusignEcologi integration FAQ
How do I add an Ecologi integration to my product?
Enable the Ecologi connector in your fastn dashboard, then let each customer authenticate their own Ecologi account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ecologi client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ecologi account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ecologi account and only ever sees their own orders, payments and customers. 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 Ecologi 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 customer's impact records before answering a question about their totals.
Who maintains the Ecologi integration?
fastn does. When Ecologi 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.
Is the Ecologi integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Ecologi integration?
A common starting point: link their own Ecologi account so contributions come from their subscription, not 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 Ecologi integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ecologi does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ecologi to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.