Bring social leads into Salesforce with context.

No. Connection setup verifies the organization, selected object and mapping. Configure and preview the relevant automation, then activate the reviewed rule to authorize the handoff. Setup alone writes no record.

Choose the object your team uses for this stage of a relationship. Scout supports Lead and Contact records, with the actual fields and requirements of the object you select. It does not automatically convert a Lead into a Contact.

The connector’s current targets are Leads and Contacts. Use those supported records for the reviewed handoff, then continue your sales process in Salesforce. No automatic Opportunity creation or custom-object destination is implied.

The Scout record key identifies the source record in your selected object. Its Salesforce field must be unique and marked as an external ID. The separate delivery ID records the operation. Both fields need room for at least 36 characters.

Your Salesforce administrator chooses or creates the fields. Scout reads their current metadata and checks that they meet the mapping requirements. Choose compatible existing fields or ask the administrator for the missing ones before verification.

Review the available source evidence. A new Salesforce record needs the values its object requires. Scout does not invent a prospect identity to fill a gap. Continue reviewing the source or choose a useful social reply when the handoff lacks required information.

The handoff uses the configured unique external-ID field containing the Scout record key. This is not a general email-based search or merge of all your Salesforce contacts. Review the selected record and operation before authorizing work.

Reviewed create-or-update work can update mapped nonblank values on the record matched by the Scout key. A create-only operation refuses an existing record. Blank values are omitted from updates. Check the actual operation’s write behavior and mapped values.

Refresh the connection and inspect the selected object’s fields again. Choose compatible writable fields, map current requirements and review the new mapping before verifying it. A stale field definition is not treated as permission to write somewhere else.

The saved operation lacks a confirmed outcome. Inspect that same operation and the destination record before taking another action. A timeout or unrecognized response is not proof that no write happened. Do not create another handoff merely to replace a missing acknowledgement.

Manage the rule in Automations and the connection in Connections. Pausing or disconnecting stops new authorized work through that rule or connection. It cannot recall a record Salesforce already accepted; inspect any in-flight or uncertain operation separately.

No. Start with Scout’s social media lead discovery and saved evidence. Connect Salesforce when you want selected records in your existing sales workflow. Every Scout plan includes connectors; choose credit capacity for your prospecting work, and keep Salesforce’s own access requirements in view.