Is it possible to add a tag to a Kajabi contact from a Pabbly workflow?

Hello Ayus,

Yes, you can apply tags to your Kajabi contacts, and Filter and Router steps in Pabbly Connect are 100% FREE and do not consume any tasks from your monthly limit.

1. How Task Counting Works

• Free Steps: Triggers, Filter by Pabbly, and Router by Pabbly do NOT count toward your monthly task quota.

• Task-Consuming Steps: Only internal Pabbly tools (like API by Pabbly) and external app action steps consume 1 task per execution.

2. Best & Most Task-Efficient Solution

Option A: Add the Tag Directly in the Kajabi Webhook (0 Extra Tasks)

Kajabi’s Offer Activation Webhook actually accepts a tags parameter directly in the payload! In your existing API by Pabbly step for the Kajabi Activation Webhook:

1. Under Set Parameters, add a new parameter label: tags

2. Set the parameter value to the tag name (e.g., Razorpay-International or Razorpay-UPI).

3. If adding multiple tags, separate them with commas (e.g., Tag1, Tag2).

• Task Impact: 0 extra tasks consumed (uses your existing Kajabi activation step).

Option B: Search Contact + Apply Tag (If Option A doesn't fit your Kajabi setup)

If you need to tag contacts independently:

1. Add the Kajabi action module: Search Contact by Email. Map the customer’s email from Razorpay to retrieve their Kajabi Contact ID.

2. Add the Kajabi action module: Add Tag to Contact using the Contact ID retrieved in Step 1.

• Task Impact: Consumes 2 extra tasks per successful transaction.

We recommend trying Option A first by simply passing the tags parameter inside your current Kajabi Offer Activation Webhook request, as it saves your task quota completely!

Please let us know if you need any assistance setting this up.

Hi Hrishabh,

Thank you for your response, but it seems both recommended options are completely non-viable for our setup—Option A does not work dynamically, and Option B requires an API access plan we do not have.

Before we look at the alternatives, let me clearly state our exact end goal so we are aligned on the required behavior:

1. Course Access (Working): Pabbly catches a Razorpay payment and grants the user a Kajabi Offer. This step works perfectly.

2. Payment Tracking (Not Working): Immediately after granting the course, we need to apply tags or track the payment method (UPI vs. Card) and its origin (International vs. Domestic Card).

3. Conditional Email Marketing (Not Working): If the customer selects "Yes" in a custom checkout dropdown on our checkout page, they must be marked as Subscribed in Kajabi. If they select "No", they must remain Unsubscribed. Crucially, both types of users must still receive their payment method tracking tags regardless of their email marketing choice.

What We Tried Instead (The Form Submission Workaround) — The Roadblock

To avoid the API restriction, we built a workaround: routing the transaction data in Pabbly and using API by Pabbly to execute an encoded form POST (application/x-www-form-urlencoded) directly to a hidden Kajabi Form endpoint:
https://kajabi.com[FORM_ID]/form_submissions

This successfully sidestepped the authentication barrier but hit two critical server-side issues inside Kajabi:

• The Email Consent Block: No matter how the text parameters are mapped (form[subscribed], form_submission[subscribed], passing boolean values, or text filters), Kajabi's endpoint server rejects external marketing opt-ins. It locks the user profile as "Never Subscribed" unless a native browser security token (Authenticity Token) accompanies the payload.

• Custom Field Limitations: Passing the parameters directly to field arrays (like form[custom_fields][custom_26]) resulted in data being dropped or ignored depending on payload formatting.

• Automation Constraints: We cannot use Kajabi's internal form automations to force the opt-in because Kajabi forms only allow subscribing users to an Email Sequence. With 15+ different courses, each requiring its own unique email sequence, this breaks our email list structure.

We Considered the Multi-Offer / Multi-Form Branching Method

We reviewed the pattern of using a Pabbly Router to split the workflow into distinct paths (UPI, International Card, Domestic Card) and connecting each path to a separate hidden Kajabi Form with dedicated native tagging automations.

However, we have two major reservations about this approach:

1. Since the basic form webhook payload is already dropping custom fields and blocking email marketing opt-ins, we are highly uncertain if splitting traffic across multiple forms will solve the core Never Subscribed webhook block.

2. Managing multiple hidden tracking forms, routers, and filters nested under 15+ different course pathways creates a massive, unsustainable architecture that is highly inconvenient to build and maintain.

Our Specific Questions for Pabbly Support:

Given that we are constrained to Pabbly Free/Growth and Kajabi Growth (No API), we need a reliable, supported data layout pattern:

1. The Exact Form Payload Syntax: What is the exact parameter Key and Value structure that Pabbly Connect needs to pass via standard urlencoded form POSTs so that Kajabi cleanly registers both a marketing email subscription (Subscribed checkmark) and writes data into custom field arrays (custom_XX) globally?

2. Alternative Zero-Task Tracking: Is there an undocumented header or alternative parameter we can include in our working Kajabi Offer Activation Webhook step to natively flag the payment type or method without using a separate action task?

3. Task-Counting Confirmation: Can you explicitly confirm that a workflow execution that triggers via our webhook but immediately terminates at a Filter step consumes exactly 0 tasks? We have roughly 21 unrelated monthly payments hitting this global webhook that must terminate at the filter level, making this vital for our capacity planning.

Please advise on the best approach for our exact software configuration.

Thanks & Regards,
Ayuskama Team

Hello,

To better understand your issue and your specific use case, we would like to schedule a call with you. You can pick a convenient time slot using the following link:

👉 Schedule a Support Call: https://www.draftmeet.com/book/lnk_07809aca15d5a864bc260f570b32bc1b

Once scheduled, we’ll discuss your workflow in detail and provide guidance to resolve the issue efficiently.

Looking forward to speaking with you.