ActionBasecampUpdated September 2026

What Basecamp projects can I access?

Short answer: You can list projects in Basecamp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Basecamp List Projects action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Projects in Basecamp — start free
Sample request
{}
Returns
[
{
"id": 555,
"name": "Marketing Site",
"status": "active"
}
]

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Projects.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about List Projects.

What does the List Projects action do in Basecamp?
Returns all active Basecamp projects the connected user is a member of. Useful for project-picker UIs in workflow setup or for cross-project reporting workflows that iterate over projects to gather metrics.
What inputs does List Projects require?
List Projects has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Basecamp returns an error?
The run history shows the failed step with its input and the error message Basecamp returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Projects support batch operations?
Run List Projects inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Basecamp's rate limits.
More actions

Other Basecamp actions.

List Projects in Basecamp — start free