Connecting Novella and Salesforce with Zapier

If your sales and customer success teams live in Salesforce, your feedback data shouldn't be stuck somewhere else. A native Novella-Salesforce integration is on our roadmap, but you don't have to wait for it. With Zapier, you can start piping NPS, CSAT, and CES data into Salesforce today, and push Salesforce data into Novella surveys in the other direction.

This guide walks through the most useful workflows and how to set them up.

Why connect Novella and Salesforce at all

Feedback data is most valuable when it sits next to the account and contact records your revenue teams already work from. A few concrete reasons to make the connection:

• Surface detractors where reps already look. A low NPS score on an account should show up as a flag in Salesforce, not buried in a separate dashboard nobody checks.
• Trigger renewal and expansion workflows from real signals. A high CSAT score after a support ticket closes is a strong expansion trigger. A detractor response ahead of a renewal date is a strong retention risk.
• Keep survey targeting accurate. Pulling fresh contact and account data from Salesforce into Novella means your surveys go to the right people, with the right context, without manual list building.
• Give account owners a single source of truth. Nobody wants to log into a third tool to check whether a customer is happy.

What you'll need

• A Novella account with API access enabled (available on all paid plans)
• A Salesforce org with API access (Enterprise, Unlimited, or Performance edition, or Professional edition with the API add-on)
• A Zapier account (the Professional plan or higher, since most of these workflows use multi-step Zaps and filters)

Workflow 1: Push new Novella responses into Salesforce

This is the most common starting point. Every time someone submits a survey response in Novella, a matching record gets created or updated in Salesforce.

Trigger: New Survey Response (Novella)
Action: Create or Update Record (Salesforce)

Steps:

1. In Zapier, create a new Zap and choose Novella as the trigger app.
2. Select "New Survey Response" as the trigger event. If you run multiple survey types, you can scope this to a specific survey.
3. Connect your Novella account using an API key generated from Settings > API Keys in your Novella dashboard.
4. Add a Salesforce action step. "Create or Update Record" is usually the right choice, since it avoids duplicate records when a contact responds to more than one survey.
5. Map the fields: survey score to a custom field on the Contact or Account object (for example, NPS_Score__c), response date, verbatim comment, and survey type.
6. Match on email address or an external ID if you're syncing against a custom object rather than standard Contact records.

A quick note on scoring types: if you run NPS, CSAT, and CES surveys through Novella, it's worth creating separate custom fields in Salesforce for each, rather than trying to force them into one generic "score" field. The scales don't mean the same thing, and your reports will get confusing fast if you blend them.

Workflow 2: Flag detractors for immediate follow-up

A general sync is useful, but the workflow that actually changes outcomes is routing detractors to the right person immediately.

Trigger: New Survey Response (Novella), filtered to NPS score 0-6
Action: Create Task or Case (Salesforce)

Steps:

1. Set up the same trigger as above, but add a Zapier Filter step right after it.
2. Configure the filter to only continue if the NPS score is 6 or below.
3. Add a Salesforce action to create a Task assigned to the account owner, or a Case if your team routes detractor follow-up through support workflows.
4. Include the verbatim response and score in the task description, and set a due date a day or two out so it doesn't get lost.

If you want more urgency, add a Slack, Teams or email notification step in parallel using Zapier's built-in paths feature, so the account owner gets pinged directly rather than relying on Salesforce task notifications alone.

Workflow 3: Sync Salesforce contacts into Novella for targeted surveys

This runs in the opposite direction. Instead of building survey recipient lists by hand, you can keep a Novella audience segment updated automatically as Salesforce records change.

Trigger: New or Updated Record (Salesforce)
Action: Create new respondent (Novella)

Steps:

1. Choose Salesforce as your trigger app and select the object you want to watch, typically Contact or a custom Customer object.
2. Narrow the trigger to a specific stage or condition if you don't want every record synced. For example, only contacts where the Account's Stage equals "Customer."
3. Add a Novella action step to create or update a contact, mapping name, email, account name, and any custom attributes you want available for survey targeting or segmentation.
4. Use those synced attributes to build targeted survey audiences in Novella, such as sending a CSAT survey only to accounts above a certain ARR threshold.

A few things to watch for

API rate limits. Salesforce enforces daily API call limits based on your edition and user count. If you're syncing at high volume, batch your Zaps or use Zapier's built-in delay and queue features rather than triggering on every single event in real time.

Field type mismatches. Novella scores are numeric, but if the Salesforce field you're mapping to was set up as text, the sync will fail silently in some cases or throw an error in others. Check your field types before your first test run.

Duplicate detection. If you're not using "Create or Update," make sure your Zap includes a lookup step first to check for an existing record. Otherwise repeat survey respondents will generate duplicate rows.

GDPR and data residency. Novella stores and processes data within the EU by default. If your Salesforce org runs on US-based infrastructure, confirm that pushing personal data across that boundary fits your data processing agreements before you turn this on for production traffic. This is worth a short conversation with whoever owns compliance on your team, not something to route around silently through an automation tool.

Where this fits with what's coming

Zapier is a solid way to get Novella and Salesforce talking today, and for a lot of teams it'll be all you ever need. For teams running high response volumes or wanting bi-directional sync without the overhead of managing Zaps, a native integration removes the extra hop and the rate limit ceiling that comes with routing everything through a third-party automation layer. We're building that next, following the same integration pattern we used for HubSpot.

If you're already running this Zapier setup and hitting friction, particularly around volume or field mapping complexity, we'd like to hear about it. It's directly shaping what the native integration needs to handle on day one.