Simplesat surveys reach your HubSpot contacts inside the emails HubSpot sends: the email your ticket pipeline sends when a ticket closes, a marketing email, or an automated email from a workflow. A HubSpot workflow can also ask Simplesat to send the survey email itself.

Connect HubSpot, and each rating lands on the HubSpot contact or ticket it belongs to, while HubSpot's ticket and contact details come back onto the response in Simplesat.

Survey code pasted into a HubSpot email works without connecting HubSpot.

The HubSpot page groups its integrations under Account-wide integrations, Survey integrations and Ticket integrations. None of them sends a survey.

Integrations under Ticket integrations run only on surveys connected to HubSpot. Those are External email embed surveys with the HubSpot Service Hub or HubSpot Email and Marketing Hub option, and Event-based surveys with Connected service set to HubSpot. Integrations under Survey integrations run on responses from any survey, however it was sent.

Every integration that runs on responses, except Add note to contact after receiving feedback, has a When should this integration run? setting. Under Let me choose, an integration runs only on the surveys you switch on, and new surveys start off. Writing feedback back, and mapping the fields covers these settings and their timing.

Create custom objects from feedback, Create follow-up tickets from feedback and Create task on contact upon receiving feedback also let you pick sentiments, with and without a comment.

Every Simplesat plan includes the HubSpot integrations. Connecting HubSpot and switching integrations on takes the Manage integrations permission in Simplesat, which Owner and Admin have by default.

Integration security, permissions and data flow covers what the connection can read and write.

A workspace connects to one HubSpot account at a time.

Once an integration is on, send a real response through it to check that it works. Testing an integration end to end walks through it.

To put a survey inside an email HubSpot sends, copy its code in Simplesat:

HubSpot then decides who gets the email and when, so Simplesat's Delay and Suppression don't apply. If you want Simplesat to send the email, use an Event-based survey that a HubSpot workflow triggers. Choosing a survey delivery method compares the options.

Use this option for the email your ticket pipeline sends when a ticket closes, or for any other email sent from a HubSpot ticket. To add the survey to the closing email:

When HubSpot sends the email, it fills in these placeholders in the survey links:

For how placeholders work across tools, see Placeholders and merge fields.

The team member is the ticket owner, matched to a Simplesat team member by email. They're credited with the role Team member until Pull ticket details changes it to Owner.

Because the ticket ID travels in the link, Simplesat keeps one response per ticket for each survey. A second rating on the same ticket updates the first response.

Use this option for marketing emails, and for automated emails a HubSpot workflow sends, which need Marketing Hub Professional or Enterprise. In HubSpot, add a custom email module with the HTML to the marketing email, or to the email the workflow sends.

The code carries the contact's email, HubSpot ID, first and last name and company, from {{contact.email}}, {{contact.hs_object_id}}, {{contact.firstname}}, {{contact.lastname}} and {{company.name}}. Those placeholders work in any workflow email. The link has no ticket or team member, so these responses get a random ticket ID that isn't a HubSpot ticket.

Every click on a rating records a new response, so a contact who clicks twice leaves two.

With this route, a HubSpot workflow calls Simplesat, and Simplesat sends the email with the survey's Delay and Suppression applied.

In Simplesat:

In HubSpot:

These emails show on the survey's Email activity. When one doesn't arrive, When a survey does not send lists what to check.

Integrations that write to a contact use the matching contact, meaning the HubSpot contact whose email is the response's customer email. If a response has no customer email, or its email isn't on a HubSpot contact, nothing is written to contacts.

Integrations that write to a ticket use the rated ticket, meaning the HubSpot ticket whose ID came in with the response. That ID comes only from the HubSpot Service Hub code, or from an Event-based request that includes it.

Simplesat writes to HubSpot no sooner than five minutes after a response arrives, and again when the response changes. A rating changed in Simplesat goes to HubSpot right away. Create follow-up tickets from feedback is the exception: it runs only when a response arrives. Notes, feedback records and tasks are created fresh on every run, so a comment that comes in after the rating adds a second one.

Keep each contact's latest feedback in HubSpot properties you choose, where you can filter, report and build workflows on it. On every run, Simplesat writes all your mapped rows to the matching contact in one update, replacing the last response's values.

Put the feedback on the ticket it's about. Simplesat writes your mapped rows to the rated ticket. Its Field mapping lists your HubSpot ticket properties and takes the same kinds of values as the contact version. Create each property on tickets in HubSpot first.

Simplesat doesn't check a property's type when you map it, and all mapped values go to HubSpot in one update. If HubSpot refuses one value, nothing in that update is written.

Your team sees the full response on the rated ticket as a note, dated when the response was created. The note opens with "customer name or email left sentiment feedback for survey name", or "Someone left" when there's no customer, and links to the customer and the response in Simplesat. Next comes every question with its answer. The metric rating shows as the rating, an emoji and its label, and follow-up answers sit under their question.

Simplesat adds a note to the matching contact with every question and its answer.

Give every response its own Simplesat feedback record in HubSpot, on the matching contact. A record holds the metric rating, its sentiment and its follow-up answer, the survey's name, and a link to the response in Simplesat.

Simplesat doesn't create the object. In HubSpot, create a custom object named Simplesat feedback, which gives it the internal name simplesat_feedback. Make Sentiment its primary display property, and give it these properties:

Then add an association with Contacts.

This integration has no Field mapping. A response without a customer email still gets a record, with no contact.

Responses arrive with the ticket, contact and owner details the survey link carried. Pull ticket details and Pull contact details then read HubSpot and update them. Attribution: linking feedback to tickets, customers and agents covers how Simplesat ties a response to a customer, a ticket and a team member.

Simplesat reads the rated ticket as soon as a response arrives, and again when the response changes, and writes to the response:

The pull replaces the response's team members and customer, and credits whoever owns the ticket when it runs. It doesn't read the ticket's priority, pipeline, stage, category or ticket properties.

If the ticket has no owner, the response still gets the ticket's contact and company. If the ticket has no associated contact, or the contact has no email, the response keeps the customer the link carried. If Simplesat can't read the ticket at all, the response keeps everything the link carried.

Simplesat updates the customer from the matching contact as soon as a response arrives, and again when it changes. The customer gets their HubSpot contact ID, their name from the first and last name, and their company from the contact's Company name property, not the associated company. The pull needs a customer email on the response. It doesn't change the ticket, the team member, or the customer's attributes and tags.

Your HubSpot contacts come into Simplesat as customers once a day, at the time of day the sync was switched on. The first run brings in up to 10,000 contacts with an email address. After that, a run brings in the contacts updated in the 24 hours before it.

Customers get their name from the contact's first and last name, their email, their HubSpot contact ID, and their company from the Company name property, not the associated company. There's no filter by list, lifecycle stage or owner, and no other HubSpot properties come in by default. We can add contact properties to the sync on request, and they come in as customer attributes. Once the sync brings in attributes, each run replaces all of a customer's attributes, including ones from a CSV import.

Contact sync from a connected tool covers what every tool's contact sync has in common.

Turn feedback into work your team sees in HubSpot: a ticket in your pipeline, or a task on the contact. Creating a follow-up ticket from feedback covers follow-ups in every tool.

Simplesat opens a HubSpot ticket when a response arrives, once per response.

The subject reads "New sentiment feedback from customer name on ticket ticket ID". The ID there is the one on the response, so it points to a real HubSpot ticket only when the survey was sent from one. The description lists the survey, the customer's name and email, the rating and its label, and the comment.

New tickets land in your default ticket pipeline with no owner or priority. They aren't associated with the contact, a company or the rated ticket, so they don't show on the contact's record. The subject, pipeline and description can't be changed in Simplesat, and there's no Field mapping. To assign the tickets or move them to another pipeline, use a HubSpot workflow.

Give someone a to-do on the matching contact when feedback comes in. The task is due 7 days after Simplesat creates it, with the status Not started and the priority Low.

The subject reads "customer name left sentiment feedback for ticket ticket ID on survey survey name". The body says who left what feedback on which survey, links to the customer and the response in Simplesat, and lists every question with its answer.

The task's owner is the response's team member, matched by their HubSpot owner ID, which a team member has once Pull ticket details has run on a ticket with an associated contact. When the response has no team member, the task is created without an owner. On surveys sent from another tool, the team member carries that tool's ID rather than a HubSpot owner ID, so if you run this integration on those surveys, set an owner in Field mapping. That owner then goes on all of the integration's tasks, not only the ones from those surveys. The same table has rows for the subject, body, due date, status, priority and task type.

To connect another HubSpot user or account:

Survey code in your HubSpot emails keeps working through the change. So does a Simplesat email from a HubSpot workflow, because it runs on a Simplesat API key.

For a new HubSpot account, or a move from a HubSpot sandbox to production:

Contact, owner and ticket IDs differ between HubSpot accounts, so IDs Simplesat saved from the old account don't match the new one.

HubSpot shows this on its own page when it refuses the connection. Connecting needs a HubSpot user with Super Admin or App Marketplace access permissions. When HubSpot's reason is about scopes, such as "Authorization failed because one or more scopes are invalid" or "Authorization failed because the provided scopes are missing", the scopes come from Simplesat's HubSpot app, not from your HubSpot role. Signing in as a different user won't change them. Contact us with HubSpot's message.

Simplesat doesn't check the connection again after you connect. If Simplesat's app is uninstalled in HubSpot, under Settings → Integrations → Connected Apps, the integrations fail and the page still reads Authenticated with HubSpot. Click Revoke access, then Authenticate, then activate each integration again. Integration error messages and what they mean explains what the page shows.

An integration turns off only when someone clicks Deactivate integration, or clicks Revoke access, which turns off every HubSpot integration. After we change one of your integrations for you, it can be off until you click Activate integration. If it still shows Inactive after you activate it, or it shows Inactive while it's writing to HubSpot, contact us with the integration's name.

A response gets a customer when the survey link carries the contact's email. HubSpot adds it from {{contact.email}} when it sends the email to a contact. Code copied from Generic Embed has no HubSpot placeholders, so copy the code from HubSpot Email and Marketing Hub or HubSpot Service Hub instead. A contact with no email address in HubSpot gives no customer either.

Pull ticket details can add a customer only when the response carries a HubSpot ticket ID, from the HubSpot Service Hub code or an Event-based request, and that ticket has an associated contact with an email. Pull contact details needs a customer email already on the response.

Code copied from Generic Embed carries no HubSpot placeholders, and in a signature it's the same in every email. A response from it has a customer only when the respondent enters their name and email. If you type an email address into the code, every response gets that address. In marketing emails HubSpot sends, the code from HubSpot Email and Marketing Hub fills in each recipient's details. In ticket emails, the code from HubSpot Service Hub does.

Field mapping lists your HubSpot properties as they were when the integration's page loaded, so reload the page after you create a property. Update contact properties with rating details lists contact properties, and Update ticket properties with rating details lists ticket properties. You can't add rows in Simplesat. A property that's still missing after a reload usually doesn't exist on that HubSpot object yet, so create it in HubSpot first. If it does exist there and still isn't listed, contact us with its internal name. Writing feedback back, and mapping the fields has more on mapping.

The property is a dropdown, and a dropdown accepts only its options' internal values. A rating of 10 written to a dropdown with the options Promoter, Neutral and Detractor is refused. An answer has to match an option's internal value exactly, punctuation included. Use a number property for a rating, or set each option's internal value to the value Simplesat sends.

HubSpot refuses the whole update, so the other properties in that mapping aren't written either. Support can read HubSpot's message in the integration's log.

Check each of these:

If all of that checks out, send us the response's link. Support can read the integration's log and re-run it once the cause is fixed.

Check each of these:

Simplesat doesn't show HubSpot's refusals. If all of that checks out, send us the response's link and support can read the log.

Check each of these:

Look for the records in your Simplesat feedback records in HubSpot, and on the record of the contact with the customer's email.

Look in your default ticket pipeline first. New tickets land there and aren't associated with the contact, so they don't show on the contact's record. Simplesat also creates a ticket only when a response arrives, not when its rating changes or a comment comes in later. Then check each of these:

If all of that checks out, send us a response's link.

The default subject of Create task on contact upon receiving feedback is "customer name left sentiment feedback for ticket ticket ID on survey survey name". Field mapping shows each of those values as a code in double braces, and HubSpot receives the subject with the values filled in. Leave the row as it is to keep the default, or type your own subject to replace it.

The first run of Sync contacts brings in up to 10,000 HubSpot contacts with an email address, because HubSpot's contact search returns no more than that. Contacts without one aren't brought in, and contacts that share an email address become one customer. Later runs bring in only the contacts updated in the 24 hours before each run, so a contact the first run missed, or one updated while the sync was off, comes in the next time it's updated. To run the first import again, click Deactivate integration, Reset integration, then Activate integration.

The integration can't raise the 10,000 limit, but a CSV import brings in the rest straight away. It merges on email address, so nobody is duplicated, and the steps are in Customers.

When feedback arrives. Contact properties, ticket properties, notes, Simplesat feedback records and tasks are written no sooner than five minutes after a response arrives, and again when it changes. A rating changed in Simplesat is written right away. Pull ticket details and Pull contact details run as soon as a response arrives. Only Sync contacts runs once a day.

You can write:

Every run replaces the last value, so the property holds the latest response. Create the property in HubSpot first, with a type that takes the value, such as a number property for a rating.

No. A run makes one record, for the metric question only. Simplesat does make another record when the response changes, such as when a comment comes in later.

Not in the integration's settings, but we add them on request. By default, the records hold the sentiment, the rating, the follow-up answer, the survey name and the link to the response, and the integration has no Field mapping. To add one, such as the customer's name or company, create the property on the Simplesat feedback object in HubSpot first, then contact us. HubSpot refuses a record that names a property the object doesn't have.

HubSpot names a record by its primary display property. With Sentiment as the primary display property, each record carries its sentiment as its name. The integration doesn't write the customer's name to the record. The customer is the contact the record is associated with.

Yes. It looks for the simplesat_feedback object every time it runs. Responses that arrive before the object exists get no record.

Yes, but not alongside production, because a workspace connects to one HubSpot account at a time. To switch, click Revoke access, then Authenticate, and choose the other account.

No. When HubSpot sends a marketing email, the survey code carries each contact's email, name, HubSpot ID and company, so responses arrive with them. Sync contacts runs once a day, at the time it was switched on, and brings in contacts updated in the 24 hours before it runs. Nothing in Simplesat shows when it last ran.

Yes. Add a t_ parameter to the end of every rating link in the copied code, for example &t_market={{contact.market}}. Change the word after t_ to the name you want in Simplesat, and the word after contact. to the property's internal name. Responses then get a ticket field with that name, holding the contact's value. In a Simplesat email from a HubSpot workflow, put the value in the request body as a custom attribute of the ticket. Placeholders and merge fields explains t_ fields. To have the property on the customer as an attribute instead, ask us to add it to Sync contacts.

Yes. Make the survey Event-based, and have the workflow call it with a custom code action, which is on HubSpot Data Hub Professional and Enterprise. Simplesat sends the email and applies Delay and Suppression. You can also paste the survey code into an automated email the workflow sends, on Marketing Hub Professional or Enterprise. In that case HubSpot decides when it goes out.

The survey code has its own inline styles, so it doesn't take on your email template's styles. Everything around it is your HubSpot email template.

Connect as a HubSpot user with Super Admin or App Marketplace access permissions. Once connected, Simplesat can reach everything its HubSpot app asks for, across the whole HubSpot account. The role of the person who connected doesn't limit it. The integrations read contacts, companies, owners, tickets, associations and custom object definitions. They create notes, tasks, tickets, custom object records and associations, and update contact and ticket properties. No integration deletes anything in HubSpot.