Feedier Surveys + Salesforce
This article covers one of the three Salesforce integration use cases: triggering a Feedier email campaign when a Salesforce record matches your conditions (e.g. a Case is closed, a Contact reaches a status). For feedback enrichment and pushing feedback back to Salesforce as FeedierFeedback__c, see Connect Salesforce to Feedier.
Who can access it?
Roles | Access |
👑 Admins | Full access |
🛠️ Editors | Full access |
👀 Viewers | No access |
🔒 Restricted viewers | No access |
On the Salesforce side, you'll need Setup access and the Flow Builder permission.
How it works
Three pieces work together:
A Feedier email campaign — the survey you want to send.
A Salesforce Outbound Message pointing to a Feedier endpoint, carrying the Salesforce fields you want to forward as feedback attributes.
A Record-Triggered Flow in Salesforce that decides when to fire the Outbound Message.
When the Flow's conditions match, Salesforce posts the selected fields to Feedier and a push is scheduled in the campaign you point to. One record → one email.
Prerequisite — Feedier email campaign
Create the email campaign in Feedier Surveys before configuring anything in Salesforce:
Step 1 — Create the Outbound Message in Salesforce
Salesforce Setup → Outbound Messages → New Outbound Message
Field | Value |
🏷️ Name / Unique Name | Any label of your choice — has no impact on the integration. |
📦 Object | The Salesforce object the Flow will run on (typically |
🚀 Endpoint URL — Production (Salesforce prod or sandbox → Feedier production) | |
🧪 Endpoint URL — Pre-production (Salesforce prod or sandbox → Feedier preprod) | |
📋 Fields to send | At minimum: the record |
Where to find the two placeholders
{FeedierCampaignID}→ Feedier → Surveys → your survey → Share → Email Campaign → Info.{FeedierPrivateAPIKey}→ Feedier → Advanced Settings → Public Key.
How the fields arrive in Feedier
Salesforce automatically prefixes every field name with sf in the XML payload it sends:
Id→sfIdContactId→sfContactIdEmail→sfEmail(orsfContactEmaildepending on the source field)Custom fields keep their
__csuffix →sfProduct_Range__c
Each of these becomes a feedback attribute in Feedier with that exact name.
⚠️ Two common gotchas:
A field that isn't ticked in the Outbound Message field list does not arrive — even if it exists on the record.
A field that is ticked but empty on the record arrives empty (and the attribute will be blank in Feedier).
Step 2 — Build the Record-Triggered Flow
Salesforce Setup → Process Automation → Flows → New Flow → Record-Triggered Flow
⚠️ Workflow Rules are deprecated by Salesforce. Use Flow Builder (Record-Triggered Flow).
Define the trigger
Pick the object that should fire the survey and choose "A record is created or updated". Add your entry conditions — for example
Case.Status = ClosedorContact.Survey_Eligible__c = true. See trigger rule examples below.Attach the Outbound Message
Add an action of type Outbound Message (under "Actions and Related Records") and select the Outbound Message you created in Step 1. Save and Activate the Flow.
Industry example (in Feedier context make sure to use the endpoints mentioned above) :
Step 3 — Test & verify
Trigger the rule on a test record (e.g. close a test Case). Then check, in Feedier:
Outbound Messages page — the parsed payload appears with status
push_created, orskipped_due_to_recently_contacted_same_campaignif a duplicate was prevented by the safety net.Pushes page — the push is scheduled and the email will be sent.
🎊 You should see a push created in the Pushes page within seconds.
Duplicate-send protection
Salesforce's Outbound Message system is built for reliability — if the response from Feedier isn't acknowledged exactly as expected, Salesforce retries the call every 2 hours for up to 24 hours. In addition, when several records are updated in the same Salesforce transaction (e.g. a bulk import), Salesforce groups them into a single Outbound Message call. Both behaviors can produce extra calls.
Feedier ships with two layers of protection:
Layer | Behavior |
🛡️ Default 24h dedupe | Same target + same push campaign within 24 hours → the second push is automatically skipped. The Outbound Message is still logged with status |
⚙️ Custom over-solicitation window | Add |
Example endpoint URL with custom over-solicitation:
Common pitfalls
Symptom | Likely cause & fix |
No Outbound Message arrives in Feedier | The Flow conditions are not matched on Salesforce side, or the message failed delivery. Check Setup → Monitor → Outbound Messages in Salesforce — failed deliveries stay in the queue for 24h with the error. |
Push created in Feedier but missing an attribute | Either the field isn't ticked in the Outbound Message's "Fields to send" list, or the field is empty on the Salesforce record. Check both — the connector forwards what Salesforce sends, nothing more. |
Examples of trigger rules
Rules live on the Salesforce side (in the Flow's entry conditions), not in Feedier:
CRM event — after a case is closed, after a purchase or order, after a support interaction, after onboarding is completed.
Segmentation — country, language, business unit, account type, subscription plan, product range.
Contact status — active client only, communication consent granted, not opted out.
Frequency — combine with Feedier's over-solicitation parameter for a survey-wide cap (e.g. one survey per contact every 90 days).
Useful Salesforce references: