I do have like wise cases and I am using custom triggers to support this. In the subscribe event you can create a webhook to an endpoint in your app (I tend to call these webhookAction). If you app should support multiple instances per board you have to think of something too prevent multiple webhooks created. My subscribe endpoint also stores a row in a local database table, that row contains accointId, boardId, maybe some config from your recipe, a triggerhook and a solutionId column. The triggerhook is set to the id returned by the create webhook. I use the same table to find out if the webhook is already created on the board (just read the database on the boardId and you know).
Then inside the webhookAction (receiving all the events) you check is the event comes from a status column. If so you can post to the action part of the recipe using the subscriptionid stored in the same database.
I don’t think you can do this with some form of persistent external storage.