Do you have documentation for all the available overrides on a trigger?
Do you have documentation for all the available overrides on a trigger?
6 Replies
Hi @J, I'm an AI assistant for Novu. While a team member reviews this question, I'll look through relevant sources and see if I can provide suggestions. Please tag @Ask Inkeep with any follow-up questions.
-----------------------------
While I generate an answer, here are some sources that might be helpful:
* Layouts
* Pushpad
* Email providers
* SMS Channel Overview
-----------------------------
Answer
Yes, the Novu documentation provides details on using overrides within a trigger event. For example, you can override the layout during a trigger event using the
layoutIdentifier property to specify which layout should be used for all emails in the context of that trigger event (1) . Additionally, there's information on setting device tokens for Pushpad integration, allowing you to target specific browsers or devices when sending push notifications by registering the Pushpad uid as the deviceToken for your Novu subscriber (2) . For email notifications, overrides can include properties like to, from, senderName, and more, allowing customization of the email sent out during a trigger event (3) . Similarly, for SMS notifications, you can use overrides to modify the to, from, and content fields of the message (4) .
For more specific overrides, such as using a SendGrid template or custom data in an email sent through Novu, you can use the customData field within email overrides to specify template details or other custom parameters required by your email delivery provider (5) .
Please refer to the Novu documentation for additional details on using overrides with different notification channels and providers.@J
For which channel specifically you are looking overrides?
@Pawan Jain The use case I have is that I want to potentially trigger an email only send for a workflow, then an in-app / other send separately. We have two different sources of subscribers which might contain duplicate emails. I can work around this with internal logic or splitting workflows, or whatever but it would be way simpler if I could just exclude specific channels from a trigger
I think I've figured out the correct solution instead of doing this. Apologies for wasting any time.
I think I should just be sending one notification, including all subscribers in the list to send to and then overriding the email settings so that only one email goes out to all users, but any other channels can use the list of subscribers to send where required.
@J, you just advanced to level 1!
Glad I could be helpful. Feel free to create a new thread with any new questions you may have.