Actions199
- Asset Category Actions
- Comment Actions
- Contact Actions
- Custom Form Actions
- Customer Actions
- Customer Asset Actions
- Customer Location Actions
- Document Actions
- KPI Actions
- Blocked Deliverables
- Expiring API Keys
- Expiring Proposals
- Expiring Warranties
- Inactive Partnerships
- Lead Pipeline Health
- Open External Tickets
- Open Tickets
- Overdue Operational Items
- Overdue Payments
- Process Bottlenecks
- Projects at Risk
- Proposals Without Activity
- Queue Health
- Revenue at Risk
- Stale Operational Items
- Stale Proposals
- Team Workload
- Unassigned Items
- Upcoming Payments
- Won Without Project Start
- Work Items Due
- Label Actions
- Lead Actions
- Lead List Actions
- Location Actions
- Operational Work Item Actions
- Payment Actions
- Process Definition Actions
- Project Actions
- Proposal Actions
- Resource Actions
- Support Request Actions
- Tag Actions
- Team Member Actions
- Timer Actions
- Work Item Actions
Operational Work Item → Reject
AI-generatedSummary
Reject an Operational Work Item by specifying its ID and a mandatory reason, optionally including geolocation data and a geo override flag.
Inputs
- Item ID (required) — The unique identifier of the Operational Work Item to reject.
- Reason (required) — The reason text explaining why the Operational Work Item is being rejected.
- Additional Fields — Optional geolocation-related additional fields: Geo Latitude, Geo Longitude, Geo Accuracy in meters, and Geo Overridden flag.
Output shape
a single record containing the response of the rejection action, typically reflecting the updated Operational Work Item or confirmation data
The output includes the node's JSON response from the API confirming rejection; no pagination or multiple items returned.