Integrating OneSignal with HubSpot
Legacy Customers only: Migrating to the new HubSpot integration
The menu of actions when both legacy and new OneSignal apps are installed. Use the one that doesn't say "Built by HubSpot".
Example migrating HubSpot workflow from legacy integration.
The HubSpot Integration card on OneSignal's Integrations page.
This will log you into HubSpot to select the account to connect with this OneSignal app.
login
method.
The OneSignal app's Workflow integration actions.
Example shows how to set the OneSignal App and External ID in the OneSignal workflow actions.
Example - OneSignal create user node in HubSpot.
{ "key1" : "value1", "key2" : "value2" }
and press Save.
You can inject HubSpot properties as tags so they are stored in OneSignal. An example of this is adding the user’s name as a tag so you can address the user by their name in their messages.
You can delete tags by setting the "value"
to an empty string like this: { "key" : "" }
. This is helpful if you have tag data in OneSignal you want deleted. If the tag doesn’t exist, it will be omitted.
Example shows setting 2 tags: "welcome" : "1" and "name" : "the First Name property as set in HubSpot". Along with the deletion of a tag called "key".
addEmail
SDK method.
Configuration of the Send OneSignal Notification action
First Name
, favorite color
) to personalize the notification fields. OneSignal will correctly format the message for different devices and messaging channels.
Click Save when finished.
HubSpot | Direction | OneSignal App | Description |
---|---|---|---|
Contacts | ➡️ | External ID | HubSpot Contact data is used to match with OneSignal users via the External ID. |
Workflows | ⬅️ | Message Templates | OneSignal Message Templates are available for selection in HubSpot Workflows |
"key"
and "value"
set in HubSpot and click Create Segment.