How to properly handle note namings?

[alfonso]

Hello everyone,

I’ve noticed that note naming has been an ongoing issue for many of us over the years, so I wanted to open a discussion about how you set proper note etiquette in your instances.

In our studio, we use a webhook that catches newly created notes that use the default naming by SG and renames them to follow a more consistent format. However, we’ve found that the email notification system within SG triggers before our webhook can rename the notes. As a result, every email notification from a new note uses the default note name, which isn’t very helpful thanks to Create’s “New note” for everything. This makes the process of reviewing notes more cumbersome and difficult to sort through on our inboxes.

I’m curious about how do you handle note naming and email notifications on your end? How do you manage this internally on your different studios?

We reached out to SG support, but their suggestion to use Zapier and overwrite email headers on top of an already complex infrastructure didn’t seem like the most elegant solution…

Thank you!!!

[Ricardo_Musch]

You can rename set the template for the Email Headers in site settings, does that help?

[alfonso]

Hey Ricardo,

We’ve played around with these settings, but wither I’m not approaching this correctly or all of this is very limited; the issue I’m running into is that I cannot poll all the information I create on my webhook renamer (i.e. the author and addressee’s departments)

[Ricardo_Musch]

Not sure I understand where you are looking.

have you tried changing the site settings for the emails?

You may be able to use deeplinks to query the data you need.

[alfonso]

You mean the placeholders? I cannot even set it to put the project.code
If it’s something else, I don’t know what you’re referring to

[Ricardo_Musch]

Wouldn’t the deeplink be {project.Project.code}?

field name → entity link → field name

EDIT
I just tried it but it doesn’t want to take it.

Would be a good feature request!