These definitions apply to all pipelines. Use field_key in the API and inbound webhooks (deal.custom_fields). Keys are set when a field is created and cannot be renamed.
Use these keys with the X-Pipeline-Api-Key header to call /api/pipeline/* from scripts and integrations. Keys are tied to your admin user and inherit the same access as your session.
— endpoints, request bodies, response samples, and curl examples.
Use this to move values stored as deal tags into a custom field (for example country tags into the Country field). Matching uses the same tag normalization as the rest of the pipeline (case and punctuation are ignored).
Add and remove tags across the selected deals. Existing tags stay untouched unless you list them under remove.
Update custom fields across the currently selected deals. For each field, choose whether to leave it unchanged, set a new value, or clear the value.
Each selected deal is assigned to one person in order: first deal to the first checked person below, second deal to the second, then the list wraps. Deal order follows the order you selected deals on the board.