Upwork TriggerInstall

Summary

Polls Upwork on the configured schedule for new jobs, message room updates, or contracts, and emits newly seen records. Choose OAuth2 or API Token credentials; for jobs, optionally provide a search query, and use the GraphQL options to customize the request and select records from its response.

Inputs

• Authentication (required) — Select OAuth2 or API Token and configure the matching Upwork credentials.
• Trigger Event (required) — Choose New Job, New Message Room Update, or New Contract. Each uses its corresponding default GraphQL query.
• Poll Times (required) — Set one or more polling intervals: every minute, 5 minutes, 15 minutes, or hour.
• Search Query — For New Job only, pass a search expression to the jobs query.
• Limit — Sets the GraphQL first variable; defaults to 25 and the UI allows 1–100.
• Variables — Provide a JSON object of GraphQL variables. These are merged after the built-in query and first variables, so supplied keys can override them.
• GraphQL Query Override — Replace the event's default GraphQL query with a custom query.
• Item Path — Select the response value to treat as records using a dot-separated path. If blank, the event's default response path is used; arrays and GraphQL connections with nodes or edges are supported.

Output shape

On polls with newly seen records, emits one n8n item per record, each containing id, resource (trigger), operation (the selected event value), data (the record), and _meta with source, fetch time, and transport. Returns no items when there are no fresh records.

The first poll initializes the seen-record cache and returns no items. Later polls suppress previously seen records, sort candidates by available creation/update/publication/start/end timestamp and then ID, and retain up to 1,000 seen identifiers per event. The default queries request one page using first; although they select pagination fields, the trigger does not fetch subsequent pages.

Links

• n8n community nodes installation guide