Trello Card Due Reminder

Remind on Trello cards due soon. This workflow lists the cards on a Trello list, filters to those due inside the next 48 hours, and notifies your team so nothing slips through the cracks.

Use case

Trello cards quietly pass their due dates when nobody is watching the board. Run this workflow on a daily (or twice-daily) schedule and InTouch will surface every card that is about to come due, delivered to your configured contacts on whatever channel they prefer (email, Slack, Discord, Telegram, SMS, etc.).

What it does each run

1. fetchCards (trello) — calls the Trello connector with operation: list-cards for the configured listId. Like every InTouch connector, it publishes exactly two outputs: result (the raw Trello API response as a JSON string) and status (the HTTP status code).
2. buildDigest (runtimeenv, python3) — parses {{fetchCards.result}}, keeps only cards whose due timestamp falls within the next 48 hours, and prints a human-readable digest. The script's stdout is published as {{buildDigest.output}}.
3. notifyDue (message) — sends {{buildDigest.output}} as the body, with the HTTP status from {{fetchCards.status}} in the subject, to the intouch user's subscribers.

If the Trello step errors, the notifications block raises an error alert to the intouch user.

Required credentials

• Trello API key — supply this yourself; never hardcode it. The fetchCards task's apiKey property is set to the placeholder "<set via credential>". Provide the real value one of two ways:
• Credential (recommended): store a Trello credential in InTouch and bind it to the task so the key is injected at run time, or
• Runtime environment variable: expose the key as an env var and reference it from the apiKey property.

Get a key/token at https://trello.com/app-key and authorize read access to your boards.

Configuration

• TRELLO_LIST_ID — the ID of the Trello list to scan. Set this as a runtime environment variable (or substitute it directly in workflow.yaml).
• Add subscribers to the intouch user so the message step has somewhere to deliver the reminder. Each contact chooses their own channel.

Scheduling

Attach a daily schedule (e.g. 8:00 AM) so the reminder lands at the start of the workday. With a 48-hour window, a daily cadence gives two heads-up notifications before any card actually comes due.