Distro can't hand off mid-flow to an external process, wait for it to finish, and then continue based on the result. Teams that run logic outside Chili Piper (an external matching agent, an enrichment service, an in-CRM process) have no native way to trigger that process from the flow, hold execution, and resume once a result comes back. The only workarounds are a blind timed delay (fragile, since the external process's timing varies and sometimes returns no result) or splitting the logic across two separate flows keyed off a field update.

Let a flow call out to an external process (e.g. via webhook), then either pause until a designated field is updated or a callback is received, or branch on the returned result, before continuing the rest of the flow.

Consolidating this into Distro removes the need to maintain external orchestration and duplicate logic. Raised by a contacts-only customer building an external contact-to-account matching agent during a 40-day LeanData replacement; they explicitly want to avoid maintaining that agent long-term and fold it into a single Chili Piper flow.