Connecting Kisi with POS for automated membership invites

Add a filter or paths step for all the purchases that don’t meet your criteria. 

​@Elevar15 

A Filter by Zapier step will give you the “do nothing” behavior you’re looking for. It stops the run when a purchase doesn’t match your membership criteria, so that purchase never reaches Kisi.

Currently, the Kisi action appears to be receiving purchases it can’t process, which causes an error. An error handler runs only after an error occurs; a Filter can prevent these purchases from reaching Kisi in the first place.

Here’s how to set it up:

1. Add a Filter by Zapier step between your POS trigger and the Kisi action.

2. Set the condition using the field that identifies the membership, such as Product Name or Purchase Name. Use Exactly matches for a specific membership name, or Contains if the name includes additional text.

3. Keep the Kisi invite action after the Filter.

Purchases that don’t meet the condition will stop at the Filter and skip the remaining steps. Matching purchases will continue to Kisi.

If different memberships require different actions, consider Paths by Zapier to create a separate branch for each membership type.

Error handlers are useful for unexpected failures, such as Kisi being temporarily unavailable.

Before setting the Filter conditions, check a few recent purchases in your trigger’s test data to confirm the exact field and membership names your POS sends.

Gaurav has the answer here. A Filter between the POS trigger and the Kisi action will stop non-membership purchases before they reach Kisi, which is cleaner than an error handler. Paths make sense if each membership type needs a different action. Checking a few recent purchases in the test data confirms the exact field and naming before you build the conditions.