Skip to content
AP3K
docs
Zapier/Trigger Zaps When Contact Tags Are Added or Removed

Trigger Zaps When Contact Tags Are Added or Removed

On this pageWhat AP3K supportsPlace the request after the tag actionExample payloadConfigure and testAvoid duplicate actions

Send a tag from a flow to another app at the point where your automation has the value it needs.

What AP3K supports

AP3K does not currently offer a native Zapier app with account-wide contact event triggers. You can send data from an AP3K flow using its External request / Zapier action. Updating a tag elsewhere does not automatically notify Zapier.

Place the request after the tag action

Use the flow’s tag action to add or remove a tag. Connect the webhook action after it and include the intended event and tag name in the request. This reports execution of that path, not every tag edit in the account.

Example payload

{"event":"tag_added","tag":"interested","email":"{{email}}"}

Configure and test

Connect the flow to a Zapier Catch Hook. Publish and run a real test interaction, then inspect the receiving record. Preview does not send an external request.

Avoid duplicate actions

A flow can reach an external request on separate runs. Design the receiving workflow to update an existing record when appropriate, and use the One DM per user rule where it fits your campaign.

Was this page helpful?