Dhiraj
NNovu
•Created by Dhiraj on 12/18/2024 in #💬│support
How to dynamically pass tags in in-app workflows?
import { workflow } from "@novu/framework";
import { payloadSchema } from "./schemas";
export const testInAppNotification = workflow(
"test-in-app-notification",
async ({ step, payload }) => {
await step.inApp(
"send-in-app",
async () => {
console.log(JSON.stringify(payload));
return {
body: payload.body,
subject: payload.subject,
avatar: payload.avatar,
redirect: payload.redirect,
primaryAction: payload.primaryAction,
secondaryAction: payload.secondaryAction,
data: payload.data,
};
},
);
},
{
payloadSchema,
tags: ["DEFAULT"]
},
);
Currently, I'm statically setting tags: ["DEFAULT"] in the workflow options.
Is there a way to dynamically pass or compute tags during the execution of the workflow? If so, could you provide an example or guidance?
3 replies
NNovu
•Created by Dhiraj on 12/5/2024 in #💬│support
Help with /v1/messages API: Stats for Email, SMS, and WhatsApp Always False
How can we get delivery and engagement stats (seen, delivered, read) for email, SMS, and WhatsApp? I tried using the /v1/messages API with the transaction ID, but the keys like seen, read, and archived are always false. Is there any Other api available
8 replies
NNovu
•Created by Dhiraj on 12/3/2024 in #💬│support
Sending WhatsApp Messages from Multiple Business Accounts in Integration Store: Feasibility and Chal
If you have multiple WhatsApp Business accounts integrated in an integration store and want to send messages using these accounts, it is crucial to understand the limitations set by the API documentation. Specifically, the inability to override the integration identifier in your requests could pose a challenge.
As per the documentation:
The integration identifier determines which WhatsApp Business account will be used.
If overriding the integration identifier is not supported, routing messages through a specific account dynamically is not straightforward.
4 replies
NNovu
•Created by Dhiraj on 11/27/2024 in #💬│support
Issue with check And Active Validation for SMS Integration
Hi, team!
I have a question regarding the parameter check And Active while creating an integration:
When I set it to true, it validates my email integration successfully, but it doesn't seem to validate for SMS. Is this expected behavior, or am I missing something in the configuration?
Would appreciate any insights or guidance!
2 replies