Not sure what Im missing here.
Have set ut a rule to send an email to the assigne of the task when its overdue.
However, I keep getting the meassge: “Provide a valid email”.
@Rune_Haarberg - I re-titled your post and moved it to the English Forum > Integrations category, as this seems like an issue with the rule action and not the trigger.
I’m wondering if it has something to do with tasks possibly not having an assignee? What happens if you move the triggerer to To: instead of CC:? (since there should always be a triggerer)
I don’t use this integration myself so can’t confirm or test; hopefully someone else can weigh in.
I’ve also not tried this integration, but I suspect that the error may caused by the lack of domain address in the To and CC email fields of the Rule, as the Outlook integration is expecting name@domain.com instead of the variable, “Assignee email”.
That being said, curious what the “Assignee Email” field is referring to. Do you have more details on this? Is it a custom field you’re using? If so, is a Text field or something else?
I’m fairly certain this is a variable accessed in the rule builder by going to the people > assignee > email. In theory, that should input a full email address to the To field, but I’m wondering if maybe adding a Check If assignee is not empty condition would solve the issue.
1 Like
I agree with @Stephen_Li I would try removing the Task Description variable in the Subject - I’m not sure it will play well with that.
Basically, @Rune_Haarberg, try each variable one by one to see which one is causing the issue.
(I have used this integration and works fine)
1 Like
This issue often arises if the task lacks an assignee or if the assignee’s email isn’t properly recognized. To address this, ensure each task has an assignee before the rule triggers. Additionally, incorporating a condition in your rule to check that the assignee field isn’t empty can help prevent this error
Is it because it’s using the rule trigger’s name instead of their email in your cc line?
I have also been getting error messages for this, but I’ve manually input emails with name@domain.com separated by semicolons.