Rules or webhook precedence?

[joeshmoe57]

I finally got around to getting a webhook set up (after leaning mostly on rules: 100+), but am struggling to understand a bit of technical detail, which I think is resulting in errors. A few ways of getting at the issue:

1. If a rule and a webhook are both set to fire on "transaction created", which executes first? Is it defined? Random / race condition?
2. Is there a way to define the behavior or set some kind of precedence? The closest I found is stopping rule execution within a group
3. If a rule and webhook fire for the same transaction, will one necessarily clobber the other?

I found some similar items, but still thought explicit answers would be helpful instead of making a better guess:

• API: Detect concurrent modifications when updating transaction #9618 seems to imply a race condition, and that there isn't currently a workaround
• Data Importer: Import transactions with tags rather than add tags right after transactions are imported #8780
• Data importer adds the "Import tag" after the rules were applied #9605

[JC5]

Hey, great questions.

1. The rules are executed first. The final result is sent to the webhook.
2. You can't change this order, but you can stop rule execution as you say.
3. No. BUT, if your webhook changes the transaction, any "update"-rules will fire after, and THAT result is shown.

I hope this helps. I'll make a note to put this in the documentation as well!