...
Add a Segment
| Info |
|---|
Feedier → Actions Feedback → Segments → New Segment |
First we need to setup a segment on Feedier. Segments are saved searches that allow you to create automisations based on your selected feedback.
...
Connect the Segment to an Automation
| Info |
|---|
Feedier → Actions Profile Name → Automations → Add Segment |
...
App Client ID | Refer to step 1, you get this from the Connected App in Salesforce. |
App Client Secret | Refer to step 1, you get this from the Connected App in Salesforce. |
Salesforce SOQL | Next Refer to next section |
Attribute Name | This is the Feedier The attribute name (not label) that contains the Salesforce object ID used for the matching. It can we receive in the feedback (for example, "sf_id") is used to match Salesforce records. This could be an Account ID, a Custom ID, a or Contact ID, etc. For example, instance, if the feedback link looks like this: In short, this attribute ("sf_id") will be used in the "WHERE" part of the Salesforce query (SOQL) |
| Info |
|---|
How to Create Your SOQL |
...
For example, the static query tested in the editor:
| Code Block | ||
|---|---|---|
| ||
SELECT Id, FirstName, LastName, Email, Phone, AccountId FROM Contact WHERE Id = '001J7000007VpctIAC' |
...
| Code Block | ||
|---|---|---|
| ||
SELECT Id, FirstName, LastName, Email, Phone, AccountId FROM Contact WHERE Id = 'sf_id' |
This dynamic approach allows you to map various Salesforce object IDs (such as Account ID, Custom ID, Contact ID, etc.) with the Feedier attribute name. The attribute name (not label) should match the Salesforce object ID used for matching purposes, ensuring seamless integration and accurate querying.
Feel free to modify or expand this as needed for your documentation.
| Note |
|---|
Important Notes |
...
Feedier will only read the first record from the query. So you can order if several records might be matched.
...
should be your final configuration :
...
| Info |
|---|
Now you just need to click save and authenticate with your Salesforce account |
How to test the integration ?
In order to test the integration, you need to go to the surveys, choose a survey that matches the segment you created, and simulate the reception of feedback with a Salesforce ID.
...
Take the link and then manually add the attribute (the name of the attribute you pass in the URL should match the one you put in the attribute name field in your integration). So, if the URL is: https://feedback.feedier.pre-prod.alkalab.com/DXoT9Z, you need to enter in your browser: https://feedback.feedier.pre-prod.alkalab.com/DXoT9Z?sf_id=001J7000007VpctIAC.
Complete the survey, and you should receive feedback with one attribute, which is sf_id.
Wait 5 minutes, and the integration should be triggered, and you should see all the attributes you included in your SOQL.
| Note |
|---|
Important Notes |
Feedier will only read the first record from the query. So you can order if several records might be matched.
The query must contain "{attribute_value}" as this attribute value will always change and be replaced automatically. It can be an ID or a value for a LIKE query/matching.
Workflow 2: Connect to Salesforce to update a ‘Salesforce Object’ post-feedback
...
This workflow is designed to send a feedback email from Feedier immediately after a certain trigger has been met on a Salesforce record.
Setup an email campaign on Feedier as a template for sending emails
| Info |
|---|
Feedier → Survey → Share → Email Campaign |
...
Setup the form as follows:
...
...
| Note |
|---|
If you are using a custom object, you need to create a custom email field to be able to attach the email to the outbound message. |
Name / Unique Name: Choose what you like, this has no impact with the connector
Endpoint URL for Sandbox : https://connector-preprod.feedier.com/salesforce/push?push_campaign_id={Feedier Campaign ID}&api_key={Private API Key Feedier}
Endpoint URL for PROD: https://connector.feedier.com/salesforce/push?push_campaign_id={Feedier Campaign ID}&api_key={Private API Key Feedier}
Add the Feedier Campaign ID from the template you just created.
...
| Info |
|---|
You can find your API details on Feedier via: |
User to send as: Choose what you like, this has no impact with the connector
Case fields to send: Choose all data you want to attach to the feedback in Feedier. ContactEmail is required.
Click Save
...
.
...
| Info |
|---|
You can find your API details on Feedier via: |
User to send as: Choose what you like, this has no impact with the connector
Case fields to send: Choose all data you want to attach to the feedback in Feedier. ContactEmail is required.
Click Save
Create the Workflow Rule
| Info |
|---|
Salesforce Process Automation → Workflow Rules |
You now need to trigger the outgoing message.
Create a trigger with your own rules (file status = closed, for example).
Attach the outgoing message you have created
...
Create a trigger with your own rules (Case status = Escalated for example)
| Note |
|---|
You can create the rule also in the Flow builder  |
Attach the outbound message to the workflow rule
| Info |
|---|
Salesforce Setup App → Workflow Rules |
Now, you need to trigger attach the Outbound message. Create a trigger with your own rules (Case status = Closed for example)message to the workflow rule so when the rule is validated an outbound message will be sent to the Endpoint URL that we set up earlier.
Attach the outbound message you created in and you're all set.
Workflow 4: If you want to pick up push status within salesforce, take a look at this guide
...
Test the outbound message
Trigger the workflow rule created and you should see a push created on the Pushes page on Feedier.