Distro Send to Router

The new Send to Router node in Distro allows you to trigger one or multiple routers directly from within an existing routing flow without relying on Salesforce helper fields or updates to start downstream routes.

This feature simplifies, speeds up, and streamlines routing by allowing you to chain routers together within Distro.

Table of Contents

• When to use Send to Router
• How to create a Router triggered by another Flow
• Adding send to the Router node to your Flow
• Viewing in Disto Router Logs

When to use Send to Router

The Send to Router node eliminates the need to trigger another router based on a field update in your CRM. Now you can seamlessly connect your Distro Routers in the flow builder.

Example use cases:

• Lead → Account routing: Match a Lead to an Account, then automatically send the Matched Account to an Account Router for ownership assignment.
• Dual routing: Route a Lead to assign the SDR in one router, then send that same Lead to another router to assign the AE.
• Multi-step routing chains: Route and enrich a record in one flow, then send it onward to another router for further action, all within Distro.
  
   

How to create a Router triggered by another Flow

Before you can send records from one router to another, your target router must be configured to start from a different flow.

1. Open your target router (for example, an Account Router).
2. Under Router Trigger Type, select “When started by another flow.”
3. Save and activate the router.
   
    

This informs Distro that this Router can be triggered by another router’s Send to Router node, rather than waiting for a Salesforce event.

Adding the Send to Router Node to Your Flow

Once your target router is set up, adding the "Send to Router" node is straightforward.

1. Open your existing Router (for example, a Lead Router).
2. At the end of your path, click + Add Node → Send to Router.
3. Choose:
   • The object or objects you want to send (e.g., Lead, Matched Account, Matched Opportunity).
   • The Router or Routers you want to trigger next.
     
      
4. (Optional) Choose whether to Skip Entry Rule or Skip Delays on the triggered router.
5. Save and test your flow.

Viewing in Disto Router Logs

Every Send to Router action is logged, making it easy to track what was sent, where it was sent, and the reason for the action.

• In the Logs, you’ll see details like:
  • Which object was sent
  • Which router was it sent to
  • The originating router and path
• You can also navigate both directions between logs:
  • From the original router to the triggered Router
  • From the triggered router back to the source

Under Actions in the original Router, you can see the send to Router details:

If you click ‘See Log,’ you can check out the triggered Router the record was sent to: