topic Re: Use value from workflow trigger action inside webhook in APIs & Integrations

Use value from workflow trigger action inside webhook

dpsk — Wed, 23 Apr 2025 06:46:13 GMT

Hello,

I'm developing a workflow that would send a webhook to our web app once a contact is added to the list. I'm mostly finished; however, I'm struggling to get an actual list ID in the webhook for the enrolled contact.

I've set up the trigger as multiple ORs for my lists. How would I know for which list the contact was actually added? Any idea how to achieve this? I can fetch the contact again, but the API does not return list memberships, and I don't want to pull every list searching.

Re: Use value from workflow trigger action inside webhook

Jaycee_Lewis — Wed, 23 Apr 2025 20:58:14 GMT

Hey, @dpsk 👋 Thanks for the interesting question. I don't see a simple unified solution here. You identified the major limitation. My gut feeling is the “easiest” way to handle this is to have a workflow per list, versus having multiple lists as enrollment options. This would make attribution easier as each list world be tied to a specific workflow and corresponding webhook.

We'll leave this open in case other community members have other suggestions for you.

Best,

Jaycee

Re: Use value from workflow trigger action inside webhook

dpsk — Tue, 29 Apr 2025 08:13:00 GMT

As I know, workflow count is limited. I'm developing this as an app on behalf of other users, so if they have many lists, this would increase workflow counts significantly, potentially even hitting the limit. I would prefer to stick to one workflow if possible.

Overall, it always feels like everything related to lists is hidden or removed from API actions. I'm not sure if this was done on purpose.

The whole reason for this workflow is simply because webhooks are missing "list" as an entity type. It would be simple to set up "Contact added to the list" type functionality via a webhook.