SupportBind a Piece to a workflow
Review supported workflow candidates and attach an approved Piece version to the exact automation or consumer that needs it.
How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Workflow bindings connect a supported Piece role with a compatible Lead360 workflow without making the Piece available to unrelated automations. Candidate discovery, draft binding, version selection, input mapping, and validation keep the relationship explicit and auditable.
When to use this workflow
Use Workflow Bindings when an Automation or other supported workflow should call a specific Piece for one defined step or responsibility.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Publish and approve the intended Piece version.
- Validate the target workflow and identify its inputs and expected outputs.
- Review user, tenant, capability, resource, and effect requirements on both sides.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the Piece workflow candidate or binding area.
- Review compatible workflow candidates in the current sub-account.
- Choose the exact workflow and supported binding point.
- Select the approved Piece version and map required inputs.
- Preview or draft the binding, then test the complete workflow and inspect its run evidence.
Understand the key controls
Candidate discovery
The product surfaces compatible candidates rather than treating every automation as a valid Piece consumer.
Version reference
The binding should identify an immutable approved version, not an unspecified future draft.
Workflow ownership
Automation Runs remains the execution source of truth, while Piece history records the role version used.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Confirm workflow, Piece version, input mapping, and tenant.
- Test expected and invalid inputs.
- Inspect the Automation Run and live final record.
Troubleshooting
The workflow is not a candidate
Check workflow type, publication, supported binding points, required inputs, and tenant compatibility.
The bound Piece receives incomplete input
Review field mapping, blank handling, trigger data, and schema changes in both the workflow and Piece.
Frequently asked questions
Can one Piece be bound to multiple workflows?
Where supported, yes, but each workflow binding should be reviewed and tested independently.
Does binding publish a draft Piece?
No. Use an approved published version and follow the workflow-specific save or deployment process.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.