EvzenSupler
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
The current implementation does not use external_user_id.
It uses the old API.
19 replies
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
I craate PR fór this issue https://github.com/novuhq/novu/pull/6794
19 replies
NNovu
•Created by EvzenSupler on 10/10/2024 in #💬│support
Workflow in dev mode
This issue was on old organization, with old api.
7 replies
NNovu
•Created by EvzenSupler on 10/10/2024 in #💬│support
Workflow in dev mode
I create new organization, and now sync working.
7 replies
NNovu
•Created by EvzenSupler on 10/10/2024 in #💬│support
Workflow in dev mode
OK I will solve this problem. I try connect to ORG which was on previous version NOVU (wihout workflow framework).
7 replies
NNovu
•Created by EvzenSupler on 10/5/2024 in #💬│support
Local development new provider and workflow
I will wait to merge
13 replies
NNovu
•Created by EvzenSupler on 10/5/2024 in #💬│support
Local development new provider and workflow
"response": {
"type": "Object",
"message": "Preferences Feature Flag are not enabled",
"stack":
"userId": "system",
"environmentId": "66ffe26cf5e234c1fa519533",
"organizationId": "66ffe26cf5e234c1fa51952c",
"key": "IS_WORKFLOW_PREFERENCES_ENABLED"
},
"status": 400,
"options": {},
"name": "PreferencesNotEnabledException"
13 replies
NNovu
•Created by EvzenSupler on 10/5/2024 in #💬│support
Local development new provider and workflow
OK when I try run workflow I get this error on my localhost:
13 replies
NNovu
•Created by EvzenSupler on 10/5/2024 in #💬│support
Local development new provider and workflow
OK I will test it
13 replies
NNovu
•Created by EvzenSupler on 10/5/2024 in #💬│support
Local development new provider and workflow
Yes, I want create new test workflow to test new provider work.
13 replies
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
Any news about Onesignal providers?
19 replies
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
In my opinion, this solution would better correspond to the current recommendation to use Onesignal integration. And it would not even require major interventions in the current solution.
19 replies
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
But as @harrisyn wrote, the best option is use external_id -Onesignal recommendation.
The user can be logged in on several devices and can receive notifications in several places. When using the Login function, an external ID is stored on Onesignal (in most cases, it is a user ID from the application database). And then it is used in the function as recommended:
replace include_subscription_ids to include_aliases with { "external_id": option.target}.
In step user novu.subscribers.setCredentials will be set Onesignal external ID as deviceTokens.
19 replies
NNovu
•Created by harrisyn on 12/16/2023 in #💬│support
OneSignal issues
Hello, now Onesignal works with Subscription ID. And use notification API from Onesignal - with DEPRECATING:
include_player_ids. Correct one options is : include_subscription_ids.
This is easy correction - rename include_player_ids to include_subscription_ids.
https://documentation.onesignal.com/reference/create-notification
19 replies