Salesforce
Send live web data to Salesforce as accounts and leads, matched to the ones you already have. Put the new leads in a campaign, and new matches keep arriving as SpecStream finds them.
SpecStream for SalesforceCRMs
What you need
- A SpecStream account, free to start, with $10 of work for new accounts and no card.
- A Salesforce user who can create accounts and leads. Some orgs need an administrator to approve an app before anyone can sign in to it.
- A collection of matches from a finished request, or an imported list once its matches are found.
- 1
1. Sign in to Salesforce
Open Connections in the workspace, find Salesforce in the catalog and click Connect. The link Connect Salesforce opens the same setup.
On the Account step, click Sign in to Salesforce. You sign in on Salesforce's own page and approve access to the API. Back in the workspace the step reads Signed in. Click Continue.
SpecStream works in the org you sign in to. Salesforce lets a connection lapse after 30 days without use. If yours lapses, sign in again from this step.
- 2
2. Choose where records go
Under Add each record as, choose Accounts or Leads. An account needs a website. A lead needs an email address its source published, and SpecStream never guesses one.
Under When Salesforce already has it, choose Fill in and update it or Leave it as it is. SpecStream searches Salesforce before it writes, so the same company is never added twice.
Salesforce campaign is optional and works with leads only. Choose Leads first, then pick one of your active campaigns. Each lead SpecStream creates or updates becomes a member of it, and leads you leave as they are don't.
In Records from, pick the collection, then tick the records to send. The list shows matches from finished requests only.
- 3
3. Match the Salesforce fields
Each row pairs a detail from your collection with a Salesforce field. SpecStream proposes the field with the same name when there is one, and you can change any of them. The menu shows fields under their Salesforce labels, custom fields included. Fields you can't both create and later change in Salesforce don't appear, and Don't send keeps a detail in SpecStream. Each field takes one detail.
To bring the pages a record was read from into Salesforce, map Why it matches, with sources to a long text field. It can run several lines.
An account always goes with its name and website. A lead always goes with its email address, a last name and a company, because Salesforce requires the last two. SpecStream takes them from the record's name and its company.
- 4
4. Review and send
Review counts the records and shows how the first one will look in Salesforce, field by field. Nothing is written until you send.
Tick Keep sending new and changed records to keep the collection feeding Salesforce. Then click Send, which shows the number of records, or Save export draft to finish later.
Each record then gets a result: Added, Updated, Already there, Skipped: no website, Skipped: no published email, Needs checking or Not delivered. Every send stays listed under Export history on the Connections page.
To send from a collection you already have, click Export on it and choose Salesforce under Send to. Sending a record again updates the same Salesforce record and adds no copy.
What arrives in Salesforce
| Detail | Accounts | Leads |
|---|---|---|
| Needs | A website | A published email address |
| Found in Salesforce by | The Website field | The Email field |
| Always sent | Name and website | Email address, last name and company |
| Left out when | No website (Skipped: no website) | The source published no email (Skipped: no published email) |
Matching
An account is searched by its Website field and a lead by its Email field. The website search covers the domain on its own and its http:// and https:// addresses, with or without www.
What happens to a match follows your choice. Updating replaces the Salesforce record's name and its matching field with this record's, along with every field you mapped. With Leave it as it is, the existing record stays untouched and the result reads Already there.
If two or more Salesforce records match, SpecStream can't tell which one is meant. That result is not written and reads Not delivered.
Campaigns
SpecStream adds each lead to your campaign as a campaign member, once. It lists your active campaigns, up to 100, and it never creates a campaign or sends email from one.
Salesforce campaigns hold leads, so the campaign picker stays off while Accounts is chosen.
When Salesforce doesn't confirm a record
If Salesforce doesn't confirm the last record, it shows Needs checking and the review step offers Check delivery. That looks for the record in Salesforce before anything is sent again.
Send waits for the check to finish, which keeps a slow answer from becoming a second record.
Keep sending
Once Keep sending new and changed records is on, new matches and changes to records already sent reach Salesforce as they arrive, with the same campaign and the same field mapping.
A sync keeps going while its list is kept current on a schedule. Watch for new ones on a list SpecStream found sets that up, and what the schedule finds follows. All plans include it. What differs is how many lists a plan keeps current at once. Schedules has the details.
Send from an agent
Signing in to Salesforce happens in the workspace. Once it's connected, an agent on SpecStream's MCP server at https://api.specstream.ai/mcp can send to it under the same rules as the workspace. Ask in plain words, for example: "Send the leads in my Austin roofers list to Salesforce and add them to my spring campaign."
The agent reads the connection with list_connections, looks at your campaigns and fields with list_connection_destinations and get_connection_columns, saves the mapping with save_connection_destination and sends with send_to_destination. create_destination_sync keeps later matches coming, and reconcile_destination_export looks for a record whose delivery wasn't confirmed. The REST API offers the same operations under /v1/connections.
Setup for each client is in the MCP guides. An API key from Agents & API keeps the permissions and spending limit you gave it.
Permissions
Salesforce asks you to approve these scopes:
api, to search accounts and leads, create and update them, list your active campaigns and add leads to one.refresh_token, to keep the connection open without asking you to sign in again each time.
What SpecStream changes in Salesforce
SpecStream works with accounts, leads, campaigns and campaign members. It does not send email.
Cost
Sending to Salesforce is free. The requests that find the data are paid from your SpecStream balance, only for the results that match, and each one shows its maximum price before it starts. Quotes and balance are explained in balance, quotes and billing.
Disconnect
Open Connections, choose the Configured tab and use the actions menu on the Salesforce row to choose Disconnect. The access SpecStream stored is deleted, and nothing more goes to Salesforce.
Salesforce isn't told. To end the authorization there as well, revoke SpecStream's access from your Salesforce user. Accounts and leads already in Salesforce stay.
Other destinations are on Connect your tools. Questions go to [email protected].
More
SpecStream for Salesforce covers what it does in Salesforce on one page. Every other tool has its guide in Connect your tools. You see the most a request can cost before it starts, and only the matches come out of your balance. Billing has the details. For help, email [email protected].