Connected processes overview
Connect processes so that reaching a specific step in one process automatically creates and tracks a linked item in another, keeping related workflows in sync.
Connected processes overview
In Kissflow, you can connect multiple processes so that actions in one process automatically initiate related items in another. When a work item in a source process reaches a step you've configured, a dependent item is created in the connected (destination) process — carrying over the field values you've mapped between them. This lets team managers and IT admins orchestrate and keep related workflows across departments in sync, without manual handoffs.
Why connect processes
- Automate item creation — when a source item reaches a configured step, a dependent item is created in the connected process automatically, cutting out manual handoffs between teams.
- Coordinate across teams — connected processes give everyone a shared, holistic view of how work moves between departments.
- Reduce errors — automating the handoff removes the chance of a step being missed or details being miscommunicated when work passes from one team to another.
Note
What happens to the source item once its dependent item is completed — whether it's automatically unblocked and resumed, or handled another way — depends on how the connected step is configured. The example below describes the common setup, where the source item pauses at the connected step until its dependent item completes.
Example: connecting Purchase Request and Purchase Order
Say your organization wants purchase orders to be created automatically once a purchase request is approved.
- An employee submits a request in the Purchase Request process, filling in details like the software needed, quantity, and justification for the purchase.
- The request moves through its approval stages. Once approved, it reaches a step named Ready for order.
- Because Ready for order is configured as a connected step, a dependent item is automatically created in the Purchase Order process as soon as the source item reaches it. Field values you've mapped between the two processes — such as software name, quantity, and cost — carry over to the new item.
- The procurement team picks up the new item in Purchase Order, reviews and finalizes the details, and sends it to the supplier.
- Once the dependent item in Purchase Order is completed, the source item in Purchase Request resumes and moves on to its next step.
What's next
- Connecting processes — set up a connected step, map fields, and configure conditions.
- FAQ - Connected processes
- Admin actions in a process — find the source and dependent items linked to any item.
- Associated flows for processes