Using filters in Zapier to connect Mighty Networks and Keap efficiently

Hi ​@COA 

You may want to look into making the Zaps more dynamic by using lookup tables:

• Zapier Tables
• Airtable
• GSheets

Core Concept: Replace Many Zaps with 1 Mapping Table

Instead of creating 1 Zap per plan, or building a single Zap with a large Filter step full of OR conditions, use 1 Zap that references a centralized lookup table.

The lookup table acts as a mapping layer between Mighty Networks plans and the actions you want to take in Keap.

Each row in the table represents 1 plan and defines what should happen when that plan is purchased.

For example, the table can map:

Plan ID or Plan Name → Keap Tag, Product Name, Access Level, or any other metadata you need.

Your Zap then works like this:

1. Trigger fires from Mighty Networks when a purchase or subscription event occurs.

2. The Zap captures the plan ID (or other stable identifier).

3. The Zap searches the lookup table for a matching row.

4. If a match is found, the Zap uses the values from that row to update the Keap contact.

5. If no match is found, the Zap safely stops.

This approach eliminates the need for multiple Zaps and avoids large, hard-to-maintain Filter steps.

When plans change, you simply update the lookup table.

You do not edit the Zap.

The result is one scalable, maintainable Zap with centralized control over all plan logic.

Hi Troy,

That sounds like the perfect solution, unfortunately, I don’t know enough about tables (translation: almost nothing!) to implememnt it quickly and I’m working on a deadline. Do you think the filters will work for now, thenn I can upgrade our Zap usage as I do learn about tables?

​@COA 

We don’t have enough context to be able to evaluate and advise about the complete filter/path logic you are trying to implement.

Hey there ​@COA 👋

If it helps we’ve got a guide on how to set up a lookup table in Zapier Tables here: Create lookup tables in Zaps

That said, if you’re wanting to only update the contact if they purchased a certain plan type then yes, in theory you could just use a filter. For the Filter I’d suggest using the (Text) Is in rule condition to check the plan that was purchased against a comma separated list of the applicable plans for that product. You can learn more about the different rules available for filters here: Filter and path rules in Zaps.

If you’d like to reduce the number of Zaps doing this sort of workflow, you could use Paths by Zapier instead of a filter to handle multiple products in a single Zap. Paths can use the same rule conditions that filters do, which would allow you to have one Zap handle the updating of the contact for multiple products. You can have up to 10 Paths in a Zap, so if you’ve got more than 10 products then you might need to have multiple Zaps still but the overall number of Zaps would be less as each could handle 10 products. If you’ve not worked with Paths before you can find out more about how to set them up here: Add branching logic to Zaps with paths.

Hope that helps. Keep us posted on how you get on with this!