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
Appointment Outcome → Delete
AI-generatedSummary
Delete an appointment outcome by ID and reassign existing appointments to a specified outcome ID.
Inputs
- authentication (required) — Authentication method for the Follow Up Boss API. Defaults to API Key if not specified. Use API Key for simple access tokens or OAuth2 for token-based authentication.
- id (required) — Identifier of the appointment outcome to delete. Can be provided as a numeric ID (validated as digits only) or selected from a list via the built-in selector which queries available outcomes using getAppointmentOutcomes.
- assignOutcomeId (required) — Identifier of the outcome ID to which existing appointments referencing the deleted outcome will be reassigned. Follows the same ID or list selection method as the primary id parameter.
Output shape
success response from the Follow Up Boss API indicating deletion completion. If assignOutcomeId is provided, the response confirms reassignment of affected appointments.
Both id and assignOutcomeId support two modes: specifying a numeric ID directly (validated as [0-9]+) or choosing from the list of available appointment outcomes fetched via the getAppointmentOutcomes method. Authentication defaults to API Key but can be switched to OAuth2 if configured for the node.