# Adding additional items to a Zapier webhook trigger

**URL:** <https://community.noloco.io/t/adding-additional-items-to-a-zapier-webhook-trigger/1955>\
**Category:** Feature Requests\
**Created:** [May 29, 2025, 2:20pm UTC](https://community.noloco.io/t/adding-additional-items-to-a-zapier-webhook-trigger/1955 "2025-05-29T14:20:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakeliddell](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/jakeliddell/32/1333_2.png) [@jakeliddell](https://community.noloco.io/u/jakeliddell)\
**Post date:** [May 29, 2025, 2:20pm UTC](https://community.noloco.io/t/adding-additional-items-to-a-zapier-webhook-trigger/1955/1 "2025-05-29T14:20:47Z")

</div>

Use case:

I need to send data to zapier when a new Partner is added to the system. This Partner data consists of 2 sets of data - the company data, in the Partner table, and the person data, in the User table.

When a new partner is created, it will have a lead partner, which is a link to a record in the user table.

But the user’s info like phone number aren’t passed to Zapier, because only the Partner record is sent, when a new partner is added.

It would be great to be able to add additional key-value pairs to the data that’s sent.

HighLevel, for example, gives the following interface, allowing pulling of data from linked records:

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/2X/c/c39bbfd0b3ee77b66905b198593cf18b8ee1c0fa.png)

---

<div class="post-metadata">

**Author:** ![fluxomate](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/fluxomate/32/1288_2.png) [@fluxomate](https://community.noloco.io/u/fluxomate)\
**Post date:** [May 30, 2025, 1:07pm UTC](https://community.noloco.io/t/adding-additional-items-to-a-zapier-webhook-trigger/1955/2 "2025-05-30T13:07:10Z")

</div>

This would be a good addition  
At the moment when we receive the webhook in zapier/ make we add another moduel/ step straight after to find that specific record in the database using the ID from the webhook, which isn’t ideal but still workable 👍
