Actions (tags, portfolios, chasing, strike levels)
Actions (tags, portfolios, chasing, strike levels)
13 articles
- Remove Customers from Portfolios in a WorkflowAutomatically remove Customers from your Portfolios thanks to Workflows.
- Applying Cross-Level Tags in WorkflowsApply invoice tags from a customer-level workflow, or customer tags from an invoice-level workflow, using cross-level tag targeting.
- Change the Pause Chasing Status in a WorkflowAutomatically change the Pause Chasing Status of your customers.
- Change the Strike level in a WorkflowAutomatically change the Strike Level of your customers.
- ERP action in the WorkflowsNo-code workflows action "ERP record" allows you to update any field, enabling complex logic and keeping systems in sync.
- Remove a Tag in WorkflowsAutomatically remove a Tag in your Workflows.
- Add a Tag in WorkflowsAutomatically add a Tag in your Workflows.
- Assign Tags to Customers with WorkflowsTag multiple customers with workflows
- Assign Tags to Customer Groups with WorkflowsTag customer groups with workflows
- Make an API Call with Kolleno WorkflowsSend HTTP requests to an external API endpoint
- Pause workflow node when customer chasing is disabledPause a workflow node when customer chasing is turned off and resume it automatically when chasing is enabled again.
- Using Template Variables in API Request Bodies for WorkflowsUse template variables in Kolleno workflows to send dynamic ERP and customer data in API calls.
- Field Value Types for “Update Record on ERP”Use type prefixes (e.g. boolean:true, integer:10) to send correctly formatted ERP field values.