So I have built a rule that sends me a reminder email and the rule should contain the date on which I have to renew a key. The date is in the asset. I have also already built a query that also gives me a date in the mail, but the date is displayed the wrong way round and with the time. Can I change this somehow? I have already tried every formatting but none of them work.
{{lookupObjects.first.DATUM}} --> 2025-07-29T00:00:00.0+0000
??? --> 29.07.2025
Hi @Antonia
You could solve this by 1st creating a variable.
Then in the email use {{<variable-name>.toDate.jiraDate}}
Does this give you the required output?
I tried it but no date will be put out.
I tried this in the mail too: {{<variable-name>.toDate.format("dd/MM/yyyy")}}, but it doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Antonia
Anything in done in an automation brach will not be usable in the main route of the automation rule.
Create the variable in the branch and the send email action asa well.
The send email action, now will only be able to use information found in the lookup action before the brach.
Anything that is done in the brach is not usable in in the sent email action.
A brach runs parallel to the main route of the rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you for your help.
So, I moved "And: Send email" into the branch and the "create variable" is above this action. But no e-mail is getting sent. When the Aciton "And: Send email" was not in the branch, emails were sent out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Antonia
Did al the conditions pass, or did one of them fail?
If a condition fails, then the conditions or actions after the failed condition will not be executed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if you place the variable creation and email action outside the branch?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I changed the entire rule and only inserted a smart value in AQL and that was enough. and in the variable the smart value was enough: “{{object. ”Key expiration date“}}”, So thank you very much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Antonia ,
You will have to convert your date to a "Date" format in order for the formatting to work.
Can you try
{{lookupObjects.first.toDate.format("dd/MM/yyyy")}}
Best regards,
Kris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thx for ur help!
I have tried it, but then no date is displayed in the mail. The attribute field is already in date format, so for the attribute you have to select the date from a calendar, it is not a text field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Antonia ,
As @Marc - Devoteam mentioned, you will probably have to put it in an automation rule variable first, before you can use it in an email.
So put this value in a variable :
{{lookupObjects.first.DATUM}}
And the in email you can use :
{{<variable-name>.toDate.format("dd/MM/yyyy")}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you, but no in the mail isn't an date.
Where in the rule should I put the action with the variable?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured it out.
Variable: {{object."Key-Ablaufdatum"}}
Mail: {{datumf.toDate.format("dd.MM.yyyy")}}
thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.