Developer Tools · Integration
Force.com
Add Force.com to your product for your customers, and give your AI agents governed access to it.
Embed a Force.com integration so your customers can work the custom applications they built on the Salesforce Platform from inside your product, not just the standard CRM objects. Every org carries its own custom objects, fields, validation rules, and Apex REST services, so object and field mapping is configuration per customer rather than code. fastn handles per-org OAuth, token refresh, and API upkeep, so onboarding an org with an unfamiliar custom schema does not need a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read and write records on their own custom objects, mapped per org rather than hard-coded.
Read object and field metadata at runtime so your product renders each org's custom schema.
Call a customer's own Apex REST service when their business logic lives on the platform rather than in standard objects.
Trigger your product when a record on a custom object is created or updated.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent inspects an org's custom object metadata before deciding which records to query.
An agent creates or updates records on custom objects within governed permissions, with each action logged.
An agent reacts to a record change on the platform and runs the next step of a workflow.
Example prompt
List the custom objects in this org, then show records created in the last week on the one holding project data.
Set up Force.com in 4 steps
- 01Open the Force.com connector from your fastn dashboard.
- 02Have each customer authenticate their Salesforce Platform org with OAuth.
- 03Map the custom objects, fields, and Apex REST services 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 Force.com integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Force.com integration without building it. Your customers connect their own Force.com account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Force.com update is not your on-call problem.
- One integration serves your product and your agents. The same governed Force.com connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHubWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to Force.com, across other categories.
Slack
Snowflake
Airtable
PostgreSQLForce.com integration FAQ
How do I add a Force.com integration to my product?
Enable the Force.com connector in your fastn dashboard, then let each customer authenticate their own Force.com account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Force.com client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Force.com account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Force.com account and only ever sees their own services, builds and deployments. 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 Force.com 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 inspects an org's custom object metadata before deciding which records to query.
Who maintains the Force.com integration?
fastn does. When Force.com 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 react to Force.com events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Force.com?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Force.com integration?
A common starting point: read and write records on their own custom objects, mapped per org rather than hard-coded. 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 Force.com integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Force.com does not change your per-connector cost. You can start free with 3 connected accounts.
Add Force.com to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.