Generate a token in HubSpot Visitor Identification
A documented HubSpot Visitor Identification operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Generate a token
- POSTChanges data · Generate
api.hubapi.com/conversations/v3/visitor-identification/tokens/create
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which HubSpot Visitor Identification operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Questions
- Can HumDay generate a token in HubSpot Visitor Identification?
- Yes. This operation is published in HubSpot Visitor Identification's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my HubSpot Visitor Identification data?
- Yes — this is a POST operation, so it changes something in HubSpot Visitor Identification. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your HubSpot Visitor Identification account.
Where this came from
Read from a published API description for HubSpot Visitor Identification at api.hubspot.com/api-catalog-public/v1/apis/conversations/v3/visitor-identification. The description above is the provider’s own wording, not ours. Last published 2022-10-31.