Automation that triggers on field update not field adding

Dear all,

I searched the forum and faq section for a ‘similar’ problem, but until know i havent found any workable solution for my challenge. So i hope you can help me to figure out the best solution.

The problem:
I have a custom field where customers fill out their bank account number, the field gets filled out perfectly in AC and so far no problem. My issue is that out administration/backoffice department want to receive an alert (mail) whenever on of the customers changes their bank account number. So this automation only needs to start when the bank number changes and does not need to start when the number is first added.

At the moment i use a Field Changes trigger for my automation where i select the field name
chose from (any value) to (any value) and runs every time the contact is updated.

I thought this would work, but the automation also starts when the field is filled the first time. So this unfortunately is not a correct solution for my problem.

The only thing i can think of is to create 2 automations:

1st automation)
Field changes trigger where i select the proper custom field name and from (any value), to (any value) and runs (the first time the contact is added.

in this automation i only add a tag to the contact and then end the automation.

2nd automation)
Field changes trigger where i select the proper custom field name and from (any value), to (any value) and runs (every time the contact is updated) and i have added a segmentation that the tag (added in automation 1) exists.

And if these values match a notification mail will be send to our backoffice.

I am still in the test process to verify this solution, but somehow i suspect there should be a better solution for this. If so i hope you can point me in the right direction.

Thank you in advance for your input.
KR Lex

1 Like

Try putting in another custom contact field Account Number LC. The LC is for last changed. then put a conditional into the automation to check if that field is blank. if it is blank have it update the field with the date and end the automation. the next time the account number field changes it will not be blank in the LC field so it will route the other branch which contains the notification to accounting.

1 Like

@eyefuze that did the trick … thank you!