#Digest do not provide actor data of an event sender

1 messages · Page 1 of 1 (latest)

onyx flicker
#

After the digest step it seems like {{actor.firstName}} (and another properties of an actor, who triggered event) - cannot be accessed inside of the {{#each step.events}} block inside of the email step

Is it possible to access such data?

static sundialBOT
#

Hi @onyx flicker, I'm an AI assistant for Novu. While a team member reviews this question, I'll see if I can find relevant sources for your question.

#

Answer

I apologize, but I couldn't find any specific information about accessing actor data within a digest step or inside the {{#each step.events}} block in an email step. The documentation doesn't directly address this particular scenario. (1)

However, it's worth noting that the actor is an important concept in Novu. An actor refers to a user or subscriber who initiates actions that trigger events within the system. Each actor is uniquely identified by an "actorId," also known as "subscriberId," which distinguishes them from others.

Actors hold user-related variables, such as subscriber properties and data payload, containing information like names, emails, and custom data. Additionally, actors can enhance notifications by allowing their avatars to be displayed, improving the context and identification of notifications.

Since I don't have a direct answer to your specific question, I suggest clicking on the "Ask for help" button to tag a team member who can review your question and provide more detailed information about accessing actor data in digest steps and email templates.

Sources
[1] Glossary

#

Feel free to tag @static sundial with additional questions.

static sundialBOT
grizzled yarrow
#

Hi @onyx flicker could you try doing {{../actos.firstName}} ?

#

#each generates a new handlebars context

red ledge
red ledge
#

@onyx flicker

Did you manage to solve this issue?

onyx flicker
#

Sorry, haven't posted my reply here
Solved it at that moment by just adding senderName to the payload and calling it a day

Not sure what actor would be exactly used if we are going one level above - is it an actor that started digest or it's literally an actor who sent the notification

If it will be the actor who sent a notification - it would be a perfect solution in this case, but "there is nothing more permanent than a temporary solution" that we already have in code 🙂

Maybe with next such issue will try approach with {{../actor.firstName}} and let you know afterwards how it went

red ledge
#

Actor is usually that user who did some action.

Like you commented you on some github issue. All users who have subscribed to receive notifications except the user who commented

#

Here you will be the actor