Actions148
- Action Plan Actions
- Action Plan Assignment Actions
- Appointment Actions
- Appointment Outcome Actions
- Appointment Type Actions
- Automation Actions
- Automation Assignment Actions
- Call Actions
- Custom Field Actions
- Deal Actions
- Deal Attachment Actions
- Deal Custom Field Actions
- Deal Pipeline Actions
- Email Marketing Campaign Actions
- Email Marketing Event Actions
- Email Template Actions
- Event Actions
- Group Actions
- Identity Actions
- Note Actions
- People Relationship Actions
- Person Actions
- Person Attachment Actions
- Pond Actions
- Reaction Actions
- Smart List Actions
- Stage Actions
- Task Actions
- Team Actions
- Team Inbox Actions
- Text Message Actions
- Text Message Template Actions
- Threaded Reply Actions
- Timeframe Actions
- User Actions
Deal Pipeline → Update
AI-generatedSummary
Update a Follow Up Boss pipeline by ID or selected list entry, optionally modifying its fields and associated stages.
Inputs
- authentication — Choose authentication method: API Key or OAuth2 (default: API Key).
- id (required) — Pipeline identifier: provide a numeric ID (validated as [0-9]+), or select from the pipeline list via the resource locator.
- updateFields — Optional collection of fields to update on the pipeline: description (string), name (string), orderWeight (string for sort order).
- stages — Optional fixed collection of stage objects (multiple values allowed). Each stage may include: closedStage (boolean), color (hex string), description (string), name (string), orderWeight (string), and id (stage ID). If id is omitted, a new stage is created and associated with the pipeline.
Output shape
The updated pipeline object returned by the Follow Up Boss API, reflecting any changes to fields and associated stages.
Authentication defaults to API Key. The
idparameter is required and supports ID-by-string or list-selection modes. Stageidomission creates new stages; inclusion updates existing ones.
Examples
Example 1: Update pipeline name and associate a closed stage
Set id to a valid pipeline ID, updateFields.name to 'New Pipeline Name', and stages[0].closedStage to true with stages[0].id set to the target stage ID.
Example 2: Create a new pipeline with initial stages
Omit stages[].id for each stage to be newly created, provide updateFields.name and updateFields.description, and set stages[].name for each desired stage.