Add context board ID to all remote options requests

Today, I’m blocked from publishing significant functionality for use in custom automations due to a requirement for a dependency on the board ID in remote options requests.

If remote options requests always sent contextBoardId with each request, like they do integrationId and recipeId - then I could provide a number of action blocks for use in custom automations that I can’t today since I’d no longer need a dependency.

I believe this would be a fairly easy enhancement to make, since the board the recipe is being created on is always known.

Hello there @codyfrisch,

I have created the request for this for our team :grin:

Thank you for the feedback!

Cheers,
Matias