15 minIntegration
Salesforce Integration
Register ABM.dev as an External Service and enrich Leads and Contacts directly from Salesforce Flows.
In this guide
- Register ABM.dev as an External Service
- Create Flow actions for enrichment
- Build an enrichment-on-create trigger
- Map enriched data to Salesforce fields
Prerequisites
- An ABM.dev account with an API key
- Salesforce Enterprise edition or higher
- System Administrator profile or "Customize Application" permission
1
Register External Service
Salesforce External Services let you call REST APIs from Flows without writing Apex. Import the ABM.dev OpenAPI spec to generate actions automatically.
- 1.Go to Setup → External Services
- 2.Click New External Service and select "From API Specification"
- 3.Paste the ABM.dev OpenAPI URL or upload the spec file
- 4.Select the Named Credential you will create in the next step
2
Create a Named Credential
Named Credentials store your API key securely so it never appears in Flow configurations.
- 1.Go to Setup → Named Credentials → New
- 2.Set the URL to
https://api.abm.dev - 3.Set Authentication Type to Custom Header
- 4.Header name:
x-api-key, value: your ABM.dev API key
3
Build a Flow
Create a Record-Triggered Flow that enriches new Leads or Contacts automatically.
- 1.Create a new Record-Triggered Flow on Lead or Contact creation
- 2.Add an Action element and select the External Service "Create Enrichment" action
- 3.Map the email field from the triggering record to the enrichment input
- 4.Add an Update Records element to write the enriched data back to the Lead or Contact
Apex callout alternative
curl -X POST https://api.abm.dev/v1/enrichments \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "person",
"input": {
"email": "jane@acme.com"
}
}'Callout Limits
Salesforce has callout limits (100 per transaction). For bulk enrichments, use the ABM.dev campaign API instead of enriching records one by one.
Troubleshooting
External Service registration fails
- • Verify the OpenAPI spec URL is publicly accessible or upload the file directly
- • Ensure the spec is OpenAPI 3.0 format (Salesforce does not support 3.1 or Swagger 2.0)
- • Check that the spec does not exceed the 4 MB size limit
Named Credential errors
- • Verify your API key is correct by testing with curl first
- • Ensure the Named Credential URL does not have a trailing slash
- • Check that the header name is exactly
x-api-key(lowercase)