Sync everyone who contacts Dixa support into HubSpot

Every hour, we add everyone who contacted support in Dixa to HubSpot and stamp their record with recent support activity, so sales and success stay in the loop.

Deterministic Code
DixaHubSpotSalesOperationsData Sync
PromptCreate

Every hour, keep my HubSpot CRM current with everyone who contacted our support team in Dixa. Run this as deterministic code on a cron trigger at the top of every hour.

First, use Dixa's "Search conversations with filters" operation to find every conversation that was closed or updated within the lookback window. Default the lookback window to the last 1 hour, but let me change it (for example to 2 hours or 24 hours) so I can widen the net or backfill.

For each conversation returned, call Dixa's "Get conversation" operation to read the requester's name and email address. Collect the requester across all matching conversations and deduplicate by email so each person is upserted only once per run. Skip any requester that has no email address, since email is the match key.

Then upsert those people into HubSpot using the "Batch Upsert Contacts" operation, matched on the email property so existing contacts are updated and brand-new contacts are created. Map the requester's name into HubSpot's firstname and lastname and set email. Send contacts in batches of up to 100 per call, chunking into multiple calls when more than 100 people were found.

On every upserted contact, stamp a last-contacted-support date property with the time of their most recent support conversation, and where the conversation exposes it, stamp the support channel (for example email, chat, or phone). Let me choose exactly which HubSpot contact properties receive these values, including the internal property names for the last-contacted-support date and the support channel, so the mapping matches the properties already set up in my HubSpot account.

This is a straightforward field-mapping data sync, so keep it deterministic with no summarization or judgement. If a run finds no closed or updated conversations, do nothing. Respect Dixa and HubSpot rate limits and page through all results.

Additional information

What does this prompt do?
  • Finds everyone who reached out to your support team in Dixa within the last hour.
  • Creates or updates their contact in HubSpot, matched by email so you never get duplicates.
  • Stamps each contact with the date they last contacted support and, when available, the channel they used.
  • Gives sales and success teams instant visibility into recent support activity right on the contact record.
What do I need to use this?
  • A Dixa account with admin access to connect it.
  • A HubSpot account where contacts can be created and updated.
  • Optional HubSpot contact properties for the last support date and support channel, if you want those stamped.
How can I customize it?
  • Choose how far back each run looks for support conversations (default is the last hour).
  • Pick which HubSpot properties get written, including the last-contacted-support date and support channel.
  • Adjust how often the sync runs.

Frequently asked questions

Will this create duplicate contacts in HubSpot?
No. We match people by email, so existing contacts are updated in place and only genuinely new people are added.
Do I need custom fields in HubSpot?
Only if you want to record the last support date or the support channel. You can point those at existing properties or create new ones, and you choose which properties get written.
How often does it run?
Every hour by default. You can change both the schedule and how far back each run looks.
What happens if someone contacted support but has no email on file?
We skip anyone without an email address, since email is how we match records to avoid duplicates.
Will this work on HubSpot Free?
Yes, as long as your plan lets you create and update contacts.

Related templates

Screen new HubSpot contacts for data breach exposure

The moment a new contact lands in HubSpot, we check their email against known data breaches and flag the high-risk ones so your team can act fast.

Have I Been Pwned
HubSpot
Slack Bot
Agentic Task
Enrich and prioritize new Help Scout tickets in Slack

The moment a new Help Scout conversation arrives, we check the customer in your CRM, flag high-value accounts, and post a priority alert to Slack before anyone touches it.

Help Scout
HubSpot
Slack Bot
Agentic Task
Screen new HubSpot companies against Companies House

Every time a new company lands in HubSpot, we look it up on the UK register, save a due-diligence summary to the record, and alert your team to any red flags.

HubSpot
Companies House
Slack Bot
Agentic Task
Turn newly incorporated UK companies into HubSpot leads

Each weekday morning, spot UK companies registered the day before in your target sectors, add the best fits to HubSpot, and recap them in Slack.

Companies House
HubSpot
Slack Bot
Agentic Task
Keep Gladly customers in sync with new HubSpot contacts

Every time you add a contact in HubSpot, we automatically create or update their Gladly profile so support always sees up-to-date customer details.

Gladly
HubSpot
Deterministic Code
Screen new HubSpot companies for security risk with Censys

Every morning we scan each new company's domain, rate its external security exposure, log the findings to the CRM record, and alert your team when a vendor looks risky.

Censys
HubSpot
Slack Bot
Agentic Task

Stop letting support conversations disappear from your CRM.

Give sales and success automatic visibility into who just talked to support, updated every hour.