Salesforce

Finseo connects to Salesforce via the native Flow HTTP Callout action introduced in Spring 23. No Apex code required. You build a Record Triggered Flow on Lead or Contact creation that POSTs the record fields to Finseo. Finseo categorizes the LeadSource into AI source buckets (ChatGPT, Perplexity, Claude, etc.) and ties pipeline revenue back to each engine.

1. 01

   Lead AI source categorization

   When a new Lead is created with LeadSource set, Finseo categorizes it into AI source buckets and tracks it in your attribution dashboard.

2. 02

   Opportunity revenue tracking

   When an Opportunity stage changes to Closed Won, Finseo ties the Amount back to the original AI source. See revenue per AI engine over time.

3. 03

   Multi-touch attribution

   Combine Salesforce Campaign Member data with Finseo AI source data to see the AI engine influence across the full B2B funnel.

4. 04

   Account based attribution

   For ABM teams, attribute account level engagement back to AI sources. See which target accounts engaged via AI search before becoming opportunities.

5. 05

   Sales rep enablement

   Reps see the AI source on each lead. Use this context to tailor outreach: a Perplexity lead has different intent than a ChatGPT lead, and very different conversion rates.

Salesforce is the dominant CRM for enterprise B2B with over 150,000 customers. Most Salesforce setups already collect LeadSource, but the data is unstructured and disconnected from marketing channel ROI reporting. Finseo categorizes LeadSource into AI source buckets and ties revenue to specific AI engines. You finally get an answer to "How much pipeline does ChatGPT drive for us?" backed by your Salesforce data.

1. 01

   Get your Finseo webhook URL

   In Finseo, click Connect on the Salesforce integration card to reveal your project specific webhook URL.

2. 02

   Create a Named Credential

   In Salesforce Setup, go to Named Credentials and create one pointing to your Finseo webhook URL with No Authentication. This lets Flow HTTP Callout reference it cleanly.

3. 03

   Create a Record Triggered Flow

   Go to Flow Builder, then New Flow, then Record Triggered Flow. Set Object to Lead, Trigger to A record is created.

4. 04

   Add an HTTP Callout action

   Add an HTTP Callout action, select your Named Credential, set Method to POST. Map Lead fields (LeadSource, Email, Name, Amount) into the JSON request body.

5. 05

   Activate the Flow

   Save and activate. Create a test Lead with LeadSource = "ChatGPT" to verify data flows to the Finseo Attribution dashboard.

Do I need Salesforce Enterprise for this?

Yes. Flow HTTP Callout is available on Salesforce Enterprise, Unlimited, and Developer editions. Professional edition does not support HTTP Callout. If you are on Professional, use Zapier or Make as a bridge to POST Salesforce data to the Finseo API.

Yes. Flow HTTP Callout is available on Salesforce Enterprise, Unlimited, and Developer editions. Professional edition does not support HTTP Callout. If you are on Professional, use Zapier or Make as a bridge to POST Salesforce data to the Finseo API.

Do I need to write Apex code?

No. Flow HTTP Callout (introduced in Spring 23) is fully no code. You configure the Named Credential and HTTP Callout action visually in Flow Builder. No Apex, no triggers, no managed packages required.

No. Flow HTTP Callout (introduced in Spring 23) is fully no code. You configure the Named Credential and HTTP Callout action visually in Flow Builder. No Apex, no triggers, no managed packages required.

What records can I attribute?

Leads, Contacts, Opportunities, and Accounts. Most teams trigger on Lead creation for new leads, Contact creation for closed Lead conversions, and Opportunity stage change for revenue events. You can build separate Flows per object.

Leads, Contacts, Opportunities, and Accounts. Most teams trigger on Lead creation for new leads, Contact creation for closed Lead conversions, and Opportunity stage change for revenue events. You can build separate Flows per object.

Can I send Opportunity Amount for revenue tracking?

Yes. Build an Opportunity Record Triggered Flow on stage change to Closed Won. Map Amount, CurrencyIsoCode, AccountId, OwnerId, and the original LeadSource (via the converted Lead). Finseo ties revenue back to the AI source automatically.

Yes. Build an Opportunity Record Triggered Flow on stage change to Closed Won. Map Amount, CurrencyIsoCode, AccountId, OwnerId, and the original LeadSource (via the converted Lead). Finseo ties revenue back to the AI source automatically.

How does Finseo categorize LeadSource values?

Finseo uses a continuously updated AI source taxonomy. Values like "ChatGPT", "AI Search ChatGPT", "Perplexity recommended", "Found via Claude" are categorized into ai_chatgpt, ai_perplexity, ai_claude buckets. Custom LeadSource picklist values are mapped automatically based on text matching.

Finseo uses a continuously updated AI source taxonomy. Values like "ChatGPT", "AI Search ChatGPT", "Perplexity recommended", "Found via Claude" are categorized into ai_chatgpt, ai_perplexity, ai_claude buckets. Custom LeadSource picklist values are mapped automatically based on text matching.

What about Salesforce Outbound Messages?

Outbound Messages send XML, which is not supported by Finseo. Use Flow HTTP Callout instead. It sends JSON, supports modern authentication, and is easier to maintain than Outbound Messages.

Outbound Messages send XML, which is not supported by Finseo. Use Flow HTTP Callout instead. It sends JSON, supports modern authentication, and is easier to maintain than Outbound Messages.

Is the integration real-time?

Yes. Flow HTTP Callouts fire within seconds of the trigger condition. Finseo processes the payload, categorizes the source, and updates the dashboard within 5 to 10 seconds.

Yes. Flow HTTP Callouts fire within seconds of the trigger condition. Finseo processes the payload, categorizes the source, and updates the dashboard within 5 to 10 seconds.

Does Finseo write back to Salesforce?

No. The current integration is one way (Salesforce to Finseo). The agent does not edit Salesforce records, opportunities, or fields. For bidirectional sync (e.g. updating Salesforce with AI visibility scores), contact us about a custom integration.

No. The current integration is one way (Salesforce to Finseo). The agent does not edit Salesforce records, opportunities, or fields. For bidirectional sync (e.g. updating Salesforce with AI visibility scores), contact us about a custom integration.