topic Re: OneSignal - send a notification based on deal based workflow in Marketing Integrations

OneSignal - send a notification based on deal based workflow

EVatsev — Fri, 06 Sep 2024 10:16:13 GMT

Hi,

We recently integrated OneSignal with HubSpot, but I can only use it in the contact based workflow. We want to send notifications to users depending on the stage they are in. And to move them through the pipeline, it needs to be a deal based workflow. So triggers for my deal workflows are contact properties, however I can't use OneSignal in deal based workflows.

Is there a workaround it? Do I need to create exactly the same triggers in a contact based workflow and then send them notifications this way?

Re: OneSignal - send a notification based on deal based workflow

franksteiner79 — Fri, 06 Sep 2024 12:57:26 GMT

Hi @EVatsev

Just out of interest - what are you sending these contacts when deal stages change?

Also what is a flow for deals?

In theory you should be able to build a number contact-based list that are taking into account the deal stages of associated deals, and then use the fact if a contact is added or removed from these lists as trigger.

What can be tricky is the following:

Can a contact have multiple active deals?
Can deals be either jump stages or move back in stages?

Thanks

Frank

Re: OneSignal - send a notification based on deal based workflow

EVatsev — Mon, 09 Sep 2024 13:43:07 GMT

Hi @franksteiner79

Thanks for the quick reply! You can find my answers below in green:

What are you sending these contacts when deal stages change? Also what is a flow for deals? - For starters - push and in-app notification. One example is: account created, but payment method not added (send a notification to add payment method). When they add payment method, they move to a next stage (ready to make transactions).

Can a contact have multiple active deals? - No, one contact can have only one app profile and by that one deal.

Can deals be either jump stages or move back in stages? - Deals can jump stages and can move back. An example is a user inactive for more than 30 days that we moved to inactive stage (never made a transactions so never was in that stage), then logged back in and is sent back to ready to book stage.

A list is a great idea! Hope my answers above help you have a better understanding of our use case.