Hotjar and Retently Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Hotjar and Retently matched by integrating their events and actions. When marketing events happen in Hotjar, update the Retently automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Hotjar and Retently

Detailed info you need to know about Hotjar and Retently integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Hotjar

    • Marketing
    • 3 triggers
    • 3 searches
    • 2 actions

    Behavior analytics platform for heatmaps, session recordings, and user feedback surveys.[5]

  • Retently

    • Marketing
    • 3 triggers
    • 17 searches
    • 16 actions

    Customer experience surveys, feedback and NPS scores.[6]

How to connect Hotjar to Retently

Set up your Hotjar and Retently integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Hotjar and Retently work in WEXTL?

WEXTL exposes actions and triggers for Hotjar and Retently that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Hotjar triggersRetently actions

Hotjar modules

  • Get a Survey Loads one Hotjar survey by its Survey ID. Output includes its Name, Type, URL, Responses URL and Questions. Use Site ID to read a survey from a different site.
  • List Survey Responses Returns the responses collected by one survey, one item per response with Answers, Country, Device, Browser and Recording URL. Set Limit to stop at a fixed number. Watch Survey Responses checks for new ones on a schedule.
  • List Surveys Finds the surveys on a Hotjar site, each with its Name, Type, URL and whether it Is enabled. Turn on With Questions to include the Questions, and use Limit to cap the results.
  • Make an API Call Runs a free-form request against the Hotjar REST API using your saved credential.
  • Perform a User Lookup Looks up the data Hotjar holds about one person in an organization, matched by Data Subject Email. Use Data Subject Site ID to User ID Map to match the user on each site, and turn on Delete All Hits to delete whatever is found immediately.
  • Watch Events Starts a workflow the moment Hotjar sends an event to your webhook. It runs instantly rather than on a schedule.
  • Watch Survey Responses Polls one survey and starts the workflow for each response added since the last check. Each item has its Answers, Country, Device and Created time. Use Limit to set how many responses a single run handles.
  • Watch Surveys Looks for surveys created on a Hotjar site since the last check and starts a run for each. Turn on With Questions to receive the Questions as well.

Retently modules

  • Add a Suppressed Domain Blocks surveys to every address on a domain matching the Pattern, with wildcards such as *.example.com. Use Category to record what kind of domain it is and Note to record why it is blocked.
  • Add a Suppressed Email Stops surveys going to one Email address. Add a Note, and turn on Delete Contact Too to remove the customer record at the same time.
  • Add Tags to a Feedback Response Labels a survey response with Tags. Use Mode to add them to the current tags or replace all tags with them.
  • Add Topics to a Feedback Response Attaches topics, each with a Name and a Sentiment, to a survey response. Set Mode to keep the topics already there or overwrite them.
  • Create or Update Customers Upserts a list of Customers in one call, creating those that do not exist and updating the ones that do.
  • Delete Customers Removes customers from Retently, a batch at a time, using their Emails.
  • Delete Feedback Deletes survey responses in one call. Each row of Records names a response by Feedback ID, or all responses of a customer by email, narrowed with Campaign, From and Until.
  • Delete Sent Surveys Removes sent surveys from the outbox in one call. Each row of Records holds a Survey ID, or an email with an optional Campaign, From and Until to remove every survey sent to that customer.
  • Get a Company Looks up a company by Company ID or Domain, returning its Company Name, Industry Name and Contacts Count.
  • Get a Customer Retrieves one customer by Customer ID with Email, First Name, Last Name and Company.
  • Get a Feedback Response Loads one survey response by Feedback ID, with the Survey ID, Customer ID and answers.
  • Get a Template Reads a survey template with its Name and the Survey Questions it contains.
  • Get Campaign Reports Returns delivery figures and a Trend for campaigns. Pick one Campaign or leave it for all, and bound the period with Start Date and End Date.
  • Get the Account Status Pings Retently to confirm the API key works, and returns the Account, Plan and Usage.
  • Get the Latest Score Returns the current Score of a Metric and the counts of Promoters, Passives and Detractors.
  • Get Trends of a Group Shows how the metrics in a trend group moved over the Date Range.
  • Import Feedback Loads historic survey answers into a Campaign from the Feedback list. Turn on Create Customers or Update Existing Customers to sync people, and Skip Duplicates to avoid repeats.
  • List Campaigns Returns your survey campaigns with Name, Metric, Type and an Is Active flag.
  • List Companies Gets customer companies with Domain and Industry Name. Use Sort to order them and Limit to cap the count.
  • List Customers Lists customers. Search by Email, a creation window of Created From to Created Until, or Property Filters with Match, and order rows with Sort.
  • List Feedback Lists survey responses, optionally for one Campaign, Email or Customer ID. Narrow the dates with Created From and Created Until, and filter on customer properties with Property Filters and Match.
  • List Sent Surveys Lists surveys already sent. Filter by Campaign, Channel, Sent By or Email, and use Sent From and Sent Until to limit the time span.
  • List Suppressed Domains Shows blocked domains with their Pattern, Category and Reason.
  • List Suppressed Emails Shows blocked addresses with their Reason, Note and Created Date.
  • List Templates Returns the survey templates in your account by ID and Name.
  • List Trend Groups Returns trend groups with Name, ID and an Is Default flag.
  • Make an API Call Runs a free-form request against the Retently REST API using your saved credential.
  • Remove a Suppressed Domain Removes a domain from the block list. Only patterns added manually can be removed.
  • Remove a Suppressed Email Removes an address from the block list.
  • Resubscribe Customers Use Emails to allow surveys again for customers. Retently skips people who unsubscribed themselves and addresses that bounced.
  • Send a Survey Sends a Campaign survey to the Recipients provided. Use Delay (Days) to hold it back.
  • Sync Customer Attributes Refreshes the stored copies of customer attributes in feedback and sent surveys. Target customers by Customer IDs or Emails, or by the Filter fields, and use Scope to refresh feedback only or sent surveys only.
  • Unsubscribe Customers Opts customers out of surveys by Emails. Add an Opt-Out Message to record why.
  • Watch New Customers Polls every so often and emits each customer added since the last run.
  • Watch New Feedback Looks on a schedule for survey responses that arrived since the last run, optionally for a single Campaign.
  • Watch New Sent Surveys Reads the outbox on a schedule and emits each sent survey it finds. Restrict it with Campaign or Channel.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Hotjar and Retently integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Hotjar and Retently on WEXTL®

Claim your 3-day trial to build Hotjar with Retently integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Hotjar and Retently.

How do I connect Hotjar and Retently?

Connect your Hotjar and Retently accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Hotjar and Retently?

Example: when the "Watch Events" trigger in Hotjar fires, WEXTL can "Add a Suppressed Domain" in Retently. Hotjar has 3 triggers (including Watch Events, Watch Survey Responses, and Watch Surveys). Retently has 33 actions (including Add a Suppressed Domain, Add a Suppressed Email, and Add Tags to a Feedback Response). Add filters and transforms between steps when you need them.[1]

Can Hotjar trigger actions in Retently, and Retently in Hotjar?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Hotjar and Retently?

No. Hotjar-to-Retently automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Hotjar integrate with Retently in real time?

Yes. Trigger-based automations start the moment Hotjar (or Retently) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Hotjar + Retently integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Hotjar with Retently?

You can build your Hotjar + Retently automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Hotjar and Retently integration.

  1. Hotjar and Retently integration source code, module specs and credentials implementation.
  2. Our Hotjar and Retently integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Hotjar and Retently, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Hotjar integration information
  6. Retently integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Hotjar and Retently integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Hotjar and Retently, or get started