Skip to main content

Salesforce - Complete guide

Import your Salesforce cases, enrich your feedback with CRM data, send feedback back to Salesforce and trigger surveys from Salesforce.

F
Written by François Forest

In short: the Salesforce integration covers 4 independent use cases. Enable only the ones you need.

Use case

What it does

Where to set it up

1. Import cases

Analyze your Salesforce tickets in Feedier

Sources → New import

2. Enrich feedback

Add Contact, Account, Case or custom object data to each feedback

Automations

3. Send feedback back

Create FeedierFeedback__c / FeedierItem__c records on a Contact, an Account or a Case

Automations

4. Trigger surveys

Send a survey when a record meets your conditions (case closed, status reached…)

Salesforce (Flow + outbound message)

Before you start

Prerequisite

Details

Feedier role

Admin or Editor (Viewers and Restricted Viewers: no access)

Salesforce account

A Salesforce administrator to install the package and create the connection

Read permissions

The connected user must be able to read the objects used: Case for the import, Contact, Account… for enrichment

Use case 4

Salesforce Setup access and the following permission: Flow Builder

Connection

Salesforce (OAuth 2.0), in Settings → Connections. Once the package is installed, no new consent is requested.

Install the Feedier package

  1. A Salesforce administrator installs the package: Install the Feedier app.

  2. Access to grant: All users (recommended) or specific users.

  3. Install it in UAT and production.

Object IDs differ between sandbox and production: testing only in UAT won't catch the discrepancies when you go live.

Error during installation? The person installing the package isn't a Salesforce administrator. Ask your admin to do it.

Create the connection

In Settings → Connections → New connection → Salesforce, authenticate via OAuth with a Salesforce administrator account. You have two options:

Option

What it does

Deploy the automatic Salesforce package (recommended)

Feedier creates the FeedierFeedback__c object (the feedback), the FeedierItem__c object (each question and answer) and the Feedier_Integration permission set (create, read, update and delete rights on both objects for the API user). Feedier also checks that this permission set is complete.

Manual Salesforce package

Your admin creates the objects, fields and relationships themselves (for example, under a strict change management policy). See use case 3, option B.

Use case 1: import your cases

  1. In Sources, click New import, choose Sync then Salesforce.

  2. Fill in the fields:

Field

What it's for

Salesforce connection

The connection to your org

Case statuses to import

For example, closed cases only

Import all case origins

Turn it off to limit the import to certain origins (email, phone, web…)

Import cases created in

The history period, for example last 6 months

  1. Choose the source, map the fields (including your custom fields), then finish.

Use case 2: enrich your feedback

Feedier reads fields from any Salesforce object (Contact, Account, Case, custom object) based on an ID already present on the feedback, and adds them as attributes.

Before

The feedback only contains the key, for example sf_contact_id

After

First name, last name, account, industry… are added as feedback attributes

Before enrichment: the feedback only contains the key.

After enrichment: Salesforce data is added as attributes.

  1. In Automations, create an automation triggered on the segment of feedback to enrich.

  2. Add the Salesforce Sync Object action.

  3. Choose the key attribute: the Feedier attribute that contains the Salesforce ID (Account ID, Contact ID, Case ID or custom ID). Its value is injected into the query via {your_attribute}.

  4. Write the SOQL query (see below).

  5. Publish, then test: import (or create) a feedback that carries the key attribute (for example contact_id = 003J7000007...) and that matches the automation's segment. The attributes appear on the feedback in about 5 minutes.

Use a stable ID rather than email. If the same address exists on several accounts (inactive contacts, multi-country, duplicates), Salesforce returns the first one found, not necessarily the right one. Use contact_id / account_id, or send all the useful attributes directly from the outbound message (use case 4).

Write the SOQL query

Prepare and validate the query in Salesforce → Developer Console → Query Editor, then paste it as is into Feedier. Reference: SOQL and SOSL documentation.

Need

SOQL query

Contact data

SELECT Id, FirstName, LastName, Email, Phone, AccountId FROM Contact WHERE Id = '{contact_id}'

Account data

SELECT Id, Name, Industry, BillingCity, BillingState, BillingCountry FROM Account WHERE Id = '{account_id}'

Contact and its parent Account (a single query)

SELECT Id, FirstName, LastName, Email, Phone, Account.Name, Account.Website FROM Contact WHERE Id = '{contact_id}'

Case and a custom child object

SELECT Id, Subject, Status, (SELECT Id, Custom_Field__c FROM Case_Extensions__r) FROM Case WHERE Id = '{case_id}'

Child relationships: in a subquery, the suffix is __r (relationship), not __c (object), and the name is often plural (Case_Extensions__r, not Case_Extension__r). Check it in Object Manager → Fields & Relationships.

Examples in the Developer Console (Contact, Account, then Contact and its Account):

Inject the Feedier attribute into the WHERE clause with {attribute_name}. Example with {salesforce_id}:

Quick test: add the key to your survey link (?salesforce_id=001J7000007VpctIAC) and answer it yourself. The attribute is attached to the feedback, the automation triggers and the enrichment runs end to end.

Use case 3: send feedback back to Salesforce

Feedier creates a FeedierFeedback__c record, and one FeedierItem__c per question and answer, attached to a Contact, an Account, a Case or any other object through a Lookup field.

Option A: automatic package (recommended)

If you chose Deploy the automatic Salesforce package, the objects, their fields and the permission set already exist. Skip to Configure the push.

Option B: manual package

Only if you declined the automatic package. A missing or misnamed field makes the push fail without any error message.

B.1 Create the FeedierFeedback object: Setup → Object Manager → Create → Custom Object. The API name must be FeedierFeedback (Salesforce calls it FeedierFeedback__c).

B.2 Add its fields:

Field

Type

Role

Created By

Lookup(User)

Required. The user who configured the connector

FeedierFeedbackId

Text(80)

The feedback ID in Feedier

FeedierCreatedAt

Date

The feedback creation date

FeedierFeedbackName

Text(80)

The record's display name

FeedierSurveyName

Text(100)

The survey name

FeedierFeedbackLink

Text(255)

The link to the feedback in Feedier

FeedierNPSScore

Number(18, 0)

The NPS score

FeedierSatisfactionRatio

Number(18, 0)

The satisfaction ratio calculated by Feedier

FeedierPushCreatedAt

Date

The creation date of the scheduled push, if any

FeedierPushStatus__c

Text(255)

The push status

LastModifiedById

Lookup(User)

Salesforce field, required

OwnerId

Lookup(User, Group)

Salesforce field, required

B.3 Add the Lookup relationship: FeedierFeedback → Fields & Relationships → New → Lookup Relationship, to the parent (Contact, Account, Case…). Without this Lookup, the connector has no parent record to point to.

B.4 Create the FeedierItem object (API FeedierItem__c), with these fields:

Field

Type

Role

FeedierItemFullName

Text(255)

The question name

FeedierItemFeedbackObjectId

Lookup(FeedierFeedback)

The parent FeedierFeedback record

FeedierItemFeedbackId

Text(80)

The feedback ID in Feedier

FeedierItemSurveyName

Text(255)

The survey name

FeedierItemType

Text(255)

The answer type (usually question)

FeedierItemValue

Long Text Area(131072)

The answer value

FeedierItemCreatedAt

Date/Time

The answer time

Configure the push

  1. In Feedier, create (or open) the segment of feedback to send.

  2. In Automations, create an automation on this segment.

  3. Add the Salesforce → Create Object action.

  4. Choose the parent object (Salesforce Relationship Object: Contact, Account, Case…).

  5. Choose the Feedier attribute that contains the Salesforce ID of this parent (for example sfid for a Contact, sfaccountid for an Account).

  6. Save, publish, then test with a response to your own address: the FeedierFeedback record appears on the parent within a few minutes.

Attach a feedback to both the Contact and the Account

  • On FeedierFeedback__c, create two Lookup fields, one to Contact, the other to Account, both optional.

  • Create two automations on the same segment: one with contact_id (Contact Lookup), the other with account_id (Account Lookup).

  • Each feedback then produces two records, and roll-up summaries on the Account can aggregate the scores of all its feedback.

Moving from UAT to production

  • Check that the FeedierFeedback__c object and the Lookup field names are identical in UAT and production.

  • Make sure the key attribute actually contains production IDs.

  • Run a real test on a production Contact before the full rollout.

Use case 4: trigger a survey from Salesforce

Three elements work together:

Element

Role

A Feedier email campaign

The survey to send

A Salesforce outbound message

Calls Feedier and carries the Salesforce fields, which become attributes

A record-triggered Flow

Decides when to send the outbound message

When the Flow's conditions are met, Salesforce sends the chosen fields to Feedier and a push is scheduled in the campaign. One record = one email.

Prerequisite: the email campaign

Create the campaign in Feedier Surveys (Share → Email campaign) before configuring Salesforce.

Step 1: create the outbound message

Salesforce Setup → Outbound Messages → New Outbound Message

Field

Value

Name / Unique Name

Free text, no effect on the integration

Object

The object the Flow will run on (Contact, Case, Opportunity, custom object)

Endpoint URL

https://connector.feedier.com/salesforce/push?push_campaign_id={FeedierCampaignID}&api_key={FeedierPrivateAPIKey} (Salesforce production or sandbox to Feedier production)

Fields to Send

At a minimum the Id and an email field. Then any field useful as an attribute: first name, account, business unit, language, custom fields (Product_Range__c…)

Variable

Where to find it

{FeedierCampaignID}

Feedier Surveys → your survey → Share → Email campaign → campaign information

{FeedierPrivateAPIKey}

Feedier → Settings → Advanced settings → API

{targetAttributeName}

Only if the object has no Email, Email__c or ContactEmail field (see below)

Specify the email field (target_attribute)

Feedier finds the email automatically if the object contains Email, Email__c or ContactEmail. Otherwise (for example a custom CaseEmailOwner field), add the raw field name to the URL, without the sf prefix:

https://connector.feedier.com/salesforce/push?push_campaign_id={FeedierCampaignID}&api_key={FeedierPrivateAPIKey}&target_attribute=CaseEmailOwner

The field must still be checked in Fields to Send: target_attribute only tells Feedier where to look for the email.

How fields arrive in Feedier

Salesforce field

Feedier attribute

Id

sfId

ContactId

sfContactId

Email

sfEmail (or sfContactEmail depending on the source field)

Product_Range__c

sfProduct_Range__c

An unchecked field doesn't arrive, even if it exists on the record. A field that is checked but empty arrives empty.

Step 2: build the Flow

Setup → Process Automation → Flows → New Flow → Record-Triggered Flow

Workflow rules are deprecated by Salesforce: use Flow Builder.

  1. Trigger: choose the object and “A record is created or updated”, then your entry conditions (for example Case.Status = Closed or Contact.Survey_Eligible__c = true).

  2. Action: add an Outbound Message action and select the one from step 1.

  3. Save and activate the Flow.

Generic Salesforce tutorial: make sure you use the Feedier URL above.

Rule type

Examples (Flow conditions)

CRM event

Case closed, purchase or order, support interaction, end of onboarding

Segmentation

Country, language, business unit, account type, subscription, product range

Contact status

Active customer, consent given, not unsubscribed

Frequency

With the over-solicitation setting (one survey per contact every 90 days, for example)

Step 3: test and verify

Trigger the rule on a test record (close a test case, for example), then check in Feedier:

Page

What you should see

Outbound messages

The message received, with status push_created, or skipped_due_to_recently_contacted_same_campaign if a duplicate was blocked

Pushes

The scheduled push, within seconds

Protection against duplicate pushes

Salesforce resends an outbound message every 2 hours for 24 hours if it isn't acknowledged exactly as expected, and groups records updated in the same transaction (bulk import) into a single call. Feedier protects your contacts at two levels:

Protection

How it works

24-hour deduplication (automatic)

Same target and same campaign within 24 hours: the second push is skipped, with status skipped_due_to_recently_contacted_same_campaign.

Over-solicitation window (optional)

Add &over_solicitation=true&survey_id={SurveyID}&interval_days={N} to the URL: a minimum delay between two pushes of the same survey, across all campaigns.

https://connector.feedier.com/salesforce/push?push_campaign_id=610&api_key=YOUR_KEY&over_solicitation=true&survey_id=1476&interval_days=100

Choose the survey language

Add &locale={code} to the URL (fr, es…). The survey must already be translated into this language: locale picks an existing translation, it doesn't translate. See Multilingual surveys.

Security, data exchanged and GDPR

Data exchanged

  • From Salesforce to Feedier: only the fields you choose to include in the outbound message or in the SOQL query (IDs, segments, account data…).

  • From Feedier to Salesforce: the FeedierFeedback__c and FeedierItem__c records (use case 3).

  • Minimization: Feedier only collects the data needed for the service. Only send the attributes useful to your analysis.

Security and infrastructure

Element

Details

Hosting

AWS Europe (Dublin and Paris)

Certification

ISO 27001

Connector tool

Self-hosted on the same infrastructure as the Feedier platform. No third party (Zapier, Make…) is involved.

Monitoring

The platform's security and monitoring rules apply to connectors.

Backups

Daily and encrypted

OAuth scope

api refresh_token id profile email address phone. The api scope gives access to Salesforce's standard REST APIs, limited to the objects the connected user can access.

Troubleshooting

Symptom

Likely cause and solution

The connection is active but no object was created in Salesforce

The background jobs failed. Wait 15 to 30 minutes, then delete and recreate the connection. Contact support if the problem persists.

The SOQL query works in Salesforce but Feedier rejects it

Almost always the relationship name: __r (often plural) in subqueries, not __c. Check the child relationship name in Object Manager.

Feedback isn't sent to Salesforce

The key attribute (sfid, sf_contact_id…) is missing or empty on the feedback: the push is skipped. This is expected behavior.

An attribute disappeared from the Create Object action list

It was hidden at the team level. Make it visible again, or use another attribute as the key.

Duplicate FeedierFeedback records, or a Salesforce error blocking the push

Often a Salesforce “Before record is saved” Flow on FeedierFeedback that rewrites an ID. Deactivate it to test, then switch it to “After record is saved”. Feedier never sets the Salesforce object ID itself.

The same email matches the wrong contact

The email isn't unique in Salesforce: use contact_id, or send the attributes from the outbound message.

The integration stopped working after a migration to a new org (or OCE)

Update all SOQL queries that contain IDs or fields specific to the old org, and revalidate each Lookup before reactivating the automations.

No outbound message arrives in Feedier

The Flow's conditions aren't met, or delivery failed. Check Setup → Monitoring → Outbound Messages: failures stay there for 24 hours with the error.

A push is created but an attribute is missing

The field isn't checked in the outbound message, or it's empty on the record.

Need help? Contact support or your Feedier project manager with the connection name, the automation ID and a sample feedback ID.


Last reviewed: November 11, 2026, version 4.23.5.

Did this answer your question?