# Make.com Recipient NOT FOUND ID is breaking scenario

**URL:** <https://community.assembly.com/t/make-com-recipient-not-found-id-is-breaking-scenario/336>\
**Category:** General\
**Created:** [June 9, 2025, 2:07pm UTC](https://community.assembly.com/t/make-com-recipient-not-found-id-is-breaking-scenario/336 "2025-06-09T14:07:38Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![allene](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.assembly.com/allene/32/28_2.png) [@allene](https://community.assembly.com/u/allene)\
**Post date:** [June 9, 2025, 3:36pm UTC](https://community.assembly.com/t/make-com-recipient-not-found-id-is-breaking-scenario/336/10 "2025-06-09T15:36:09Z")

</div>

> [@Mallory\_Durrick](#):
>
> If I use the Universal ‘Make an API’ call, I’m wondering if this will impact the rest of my scenario which only runs 1x/day and only triggered by the invoice in 3 days time.

@Mallory_Durrick Just saw this - if you use a router to run both client and company recipient workflows, your original workflow can remain the same, and the router will only run the company workflow if the recipient ID is a company.

Or, you could set up a separate scenario for company recipients which might be less complex than using the router solution.

---

_[View the full topic](https://community.assembly.com/t/make-com-recipient-not-found-id-is-breaking-scenario/336)._