CRM & Sales · Integration
Iress Xplan
Add Iress Xplan to your product for your customers, and give your AI agents governed access to it.
Embed an Iress Xplan integration so advice firms using your product can work their own client records without switching systems. Every Xplan instance is configured differently, so field mapping is configuration per customer rather than code, and onboarding a firm with an unusual setup does not require a deploy on your side. fastn handles per-customer authorisation, token refresh, and API upkeep, and records can be read, written, and reacted to through triggers.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own client records and contact details into your product, mapped to their fields.
Write notes back so interactions captured in your product appear on the client file.
Create or update tasks so advisers work follow-ups from your product without switching tools.
Trigger your product when a client record or task is created or updated.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a client's record and recent notes before drafting a follow-up summary.
An agent creates a note or task within governed permissions, with every action logged.
An agent reacts to a client record change and runs the next step of a workflow.
Example prompt
Show clients with no recorded interaction in the last six months and list the tasks still open on each.
Set up Iress Xplan in 4 steps
- 01Open the Iress Xplan connector from your fastn dashboard.
- 02Have each customer authenticate their own Xplan instance.
- 03Map the client, contact, note, and task fields 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 Iress Xplan integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Iress Xplan integration without building it. Your customers connect their own Iress Xplan 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 Iress Xplan update is not your on-call problem.
- One integration serves your product and your agents. The same governed Iress Xplan 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
Salesforce
DealCloud
HubSpotOften used alongside
Tools the same teams tend to run next to Iress Xplan, across other categories.
Slack
Mailchimp
Marketo
Google AdsIress Xplan integration FAQ
How do I add an Iress Xplan integration to my product?
Enable the Iress Xplan connector in your fastn dashboard, then let each customer authenticate their own Iress Xplan account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Iress Xplan client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Iress Xplan account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Iress Xplan 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 Iress Xplan 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 client's record and recent notes before drafting a follow-up summary.
Who maintains the Iress Xplan integration?
fastn does. When Iress Xplan 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 Iress Xplan 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 Iress Xplan schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Iress Xplan, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Iress Xplan do not drift apart.
What can I build with the Iress Xplan integration?
A common starting point: read their own client records and contact details into your product, mapped to their 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 Iress Xplan integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Iress Xplan does not change your per-connector cost. You can start free with 3 connected accounts.
Add Iress Xplan to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.