Software Teams ClickUp Trigger
AI-generatedSummary
Polls ClickUp for tasks carrying the configured pickup tag and emits each matching ticket to start a workflow run. For each task, it fetches ticket details and prepares a support-triage input using the configured prompt, agent ID, and ticket budget.
Inputs
- Poll Times (required) — Schedule for polling, such as every minute, hourly, or a custom cron expression.
- Workspace ID (required) — Numeric ClickUp workspace ID to search.
- Pickup Tag (required) — Exact tag that a task must carry to be eligible.
- List IDs — Optional comma-separated ClickUp List ID allowlist; blank searches any list the credential can read.
- Include Closed Tickets — Whether tagged closed tasks are eligible; defaults to false.
- Process Existing Tagged Tickets on Activation — Whether to process the current tagged backlog on first activation; defaults to false.
- Max Tickets per Poll — Maximum tickets emitted per poll, from 1 to 50; defaults to 10. Tasks sharing an update timestamp are retained across polls when the cap splits that group.
- Support Prompt (required) — Prompt used to triage each ticket.
- First Agent ID (required) — Agent ID used for the ticket's first Claude turn.
- Ticket Budget USD (required) — Cumulative API-equivalent cost limit across the ticket's Claude turns.
Output shape
A list of n8n items, one per processed ticket.
Each item contains a support-ticket envelope built from the ClickUp task. Polling retains its timestamp and IDs to avoid losing tasks at a batch boundary. A task that cannot be fetched is emitted as an error item so it can be reviewed without blocking later tasks. The first activation establishes a current-time boundary unless backlog processing is enabled.