Handling custom fields in workflow

  • 5 June 2020
  • 1 reply

We have multi tenant application and each tenant has ability to create their own custom fields based on their business needs. There's no limit on number of fields one tenant can create. So far we have seen few hundreds of custom fields for each tenant. So tenant A can create custom field X1 and tenant B can create custom field Y1.

We are trying to figure out how we can plan to build both triggers & actions so that we can effectively involve custom fields in both triggers & actions. So when tenant A uses the zap, his custom fields (more than one) will be involved and similarly for tenant B her custom fields (more than one) gets involved.

Each of these tenants when using the zap should be able to map custom fields of our application with other application like we do when we are dealing with normal/system fields.

Any help in this regard will be appreciated.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

Userlevel 7
Badge +12

Hi @convergehub!


We have some guides on how to use custom/dynamic fields in your Zapier integration. I’m not sure whether you’re using the Visual Builder or CLI, so here’s the guide for both:


For the Visual Builder: How to add Dynamic and Custom fields

If you’re building with the CLI: Custom and Dynamic fields