Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi,

I want to add in our Cli integration a search field to fetch additional data, which I have added via:

 

search: {
		display: {
			label: 'Find Group',
			description: 'Search for a group by the id',
		},
		operation: {
			inputFields:  
				{
					key: 'id',
					label: 'group ID',
					type: 'integer',
					required: false,
				},
			],
			perform: (z, bundle) => {
				return utils.makeApiRequest({
					endpoint: `foo/groups`,
					paginated: true
				}, z, bundle );
			}
		}
	},

 

 

but it results in a search OR create one if none are found.

Is there a way to disable this? The module has indeed a create method, but I really don’t want to use it within the search.

First idea that springs to mind is to not implement it as a resource, but rather discrete trigger, action, search elements. You’ll get more control and less automatic magic, which is what resources are about. 

 

Terms & Conditions