Short answer: You can list jobs in Ashby by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Ashby List Jobs action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Status filter (Open/Closed) status | string | Optional | – |
{"status": "{{trigger.status}}"}
{"results": [{"id": "job_abc","team": {"name": "R&D"},"title": "Engineer","status": "Open"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.