Use this article to understand what Fin can and can't do on HubSpot. This article is for admins who have set up, or are setting up, Fin on HubSpot. These are platform constraints, not settings you can change.
Tickets and conversations
Can Fin reply to a ticket that has no conversation thread?
No. Fin replies into a conversation, so a ticket created by a workflow, an import, or directly on a record has nothing for Fin to reply to.
This most often affects forms. Two setups behave differently:
Form connected as a channel on your inbox — HubSpot creates a conversation containing the submission, Fin picks it up, and replies by email because the Forms channel can't send. Make sure the form collects an email address. This works today.
Form details written into a ticket description or note by a workflow — there's no conversation, so Fin can't reply. HubSpot's API doesn't allow creating one.
Tip: Add the form as a channel on your inbox. If you can't — because the same form also routes to your contracted plan team — let Fin triage and tag the ticket so your own routing can act on it.
Can one conversation map to more than one ticket?
No. One conversation maps to exactly one ticket, and there's no multi-party or loop-in flow.
Handoff
Can I have Fin's summary in English if the conversation was in another language?
No. Fin's summary stays in your customer's language.
Rollout
Can I roll Fin out gradually, or test it on a subset?
There's no built-in gradual rollout, and there are no test environments currently. When you set Fin live it joins live, in-progress conversations straight away.
Tip: You can approximate a controlled test by adding a filter to your own HubSpot routing so only tickets matching your test criteria reach Fin. Remove the filter when you're happy.
Do usage limits act as a kill switch?
No. A usage limit only applies to new conversations and can't cap spend mid-conversation. To stop Fin, pause the channel.
Data
Can I redact PII before Fin sees it?
No, and middleware won't achieve it. Fin uses HubSpot's webhook only as a trigger, then reads the conversation from HubSpot's API, so it never receives a payload you could intercept. This means PII (personally identifiable information) cannot be redacted before Fin processes it.
Can imported conversations be deleted?
No. If you need customer data removed, ask about redaction rather than deletion.
Does write-back update existing contacts?
No. New attributes appear on new contacts only; there's no backfill.
Reporting and channels
What isn't available on HubSpot?
Copilot (Fin's AI assistant for teammates), HubSpot's native chat widget, and Slack are not available. Fin's own CSAT (customer satisfaction survey) doesn't run on HubSpot email or tickets — use HubSpot's native CSAT instead.
Can I export full conversation threads?
Only the initial message is exportable from the portal. Full threads need the API.
Why are Insights and topics empty?
They need Fin live for around a week, with roughly 90 days of history, before they populate.
FAQs
Is there a way to test Fin on HubSpot before going fully live?
There's no built-in test environment, but you can approximate a controlled rollout. Add a filter to your HubSpot routing so only tickets matching specific criteria reach Fin. Remove the filter once you're confident in the results.
Why can't Fin reply to tickets I created through a workflow?
Fin replies into conversation threads. A ticket created by a workflow, an import, or directly on a record has no thread, so there's nothing for Fin to reply to. Connect your form as a channel instead to create the conversation Fin needs.
Can Fin summarize a conversation in English even if the customer wrote in French?
No. Fin's summary stays in the language the customer used.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts