Skip to content
AP3K
docs
Flow Builder/Action Node: Tags, Custom Fields and API Requests

Action Node: Tags, Custom Fields and API Requests

On this pageSetupAvailable actionsSetting a fieldTags versus custom fieldsSending an external requestExample flow

While other nodes control where a flow goes, actions change what AP3K knows about a contact or send data to an external service.

Setup

Add an action from the canvas, select its type and configure it in the node editor. Connect another action after it when several operations need to run in order.

Available actions

ActionWhat it does
Contact tagAdds or removes a tag.
Set custom fieldSaves a field value for later messages and conditions.
External request / ZapierSends a JSON POST request to a public HTTPS webhook.

AP3K does not provide a Delete contact flow action. Manage contacts from the Contacts page instead.

Setting a field

Enter the field name and the value to save. Use the same name in later collection steps, conditions and message tokens. Instagram profile fields are reserved and cannot be overwritten with a custom-field action.

Tags versus custom fields

Tags are labels, and a contact can have several. Custom fields hold values such as language, membership tier or campaign source. Use tags to segment; use fields to store.

Sending an external request

Use a public HTTPS URL on port 443 and a JSON object body. Variables belong inside JSON string values. This action uses POST and does not offer custom request headers. Do not paste credentials into a message or a public link.

The label mentions Zapier because a compatible webhook can receive the request; AP3K does not supply the separate native Zapier app described by some migration guides.

Example flow

Incoming DM → Collect email → Set campaign field → Add interested tag → Send confirmation. Review the contact record after testing to confirm that the right person’s data was updated.

Was this page helpful?