Due date automations do not register when a card is created with a due date

Issue Summary

When creating a card and adding a due date simultaneously through the Trello API, Automation doesn’t execute due date commands as expected. This issue occurs when both actions—creating the card and setting its due date—are performed in a single API call.

Steps to Reproduce

1. Execute an API call to create a new card on Trello, incorporating a due date in the same request.

    curl -X "POST" "https://api.trello.com/1/cards?key=[YOUR_KEY]&token=[YOUR_TOKEN]"
   -H 'Content-Type: application/json; charset=utf-8'
   -d $'{ "name": "test", "idList": "[LIST_ID_PLACEHOLDER]", "due": "[FUTURE_DATE]" # Example: "2029-06-29T16:41:30.000Z" }' 

2. Observe the behaviour of Automation related to due date commands for the newly created card.

Expected Results

Automation should recognize and run any due date commands associated with the new card, triggered by the setting of its due date.

Actual Results

Automation doesn’t execute due date commands for the card created and assigned a due date in a single API call.

Workaround

For now, To make sure the automation processes due date commands, incorporate a two-step process in the API Create card workflow:

• Create the card without a due date.

• Once the card is created, make a separate API call to add the due date to the card.