Do not open ticket automaically in form i f the requester already exists

Hey @matan12 - 

When using Zapier to automate ticket creation in Zendesk, you can set up conditions to determine whether a new ticket should be created based on certain criteria, such as whether the requester already exists (although I'm not sure I quite understand the use case here).. This typically involves using Zapier's built-in logic to check if an existing record matches the data you're about to upload.

Here are the steps you might follow to set up a condition in Zapier to prevent ticket creation if the requester already exists:

1. Search for Existing User: Before creating a ticket, add a step in Zapier that searches for users in Zendesk using the requester's email address or another unique identifier.

2. Use Filters: If the user exists, use a Zapier Filter to stop the Zap from continuing to the ticket creation step.

3. Conditional Logic: If the search finds an existing user, you could apply logic such as:

   • Do nothing, effectively skipping the ticket creation.
   • Update the existing user's information or add a comment to an existing ticket.
   • Create a ticket with a specific tag that signifies it's from a known requester.

4. Create Ticket: If no existing user is found, then continue to the ticket creation step.

Please note that this logic assumes that your definition of an existing requester is based on a unique identifier that can be searched via the Zendesk API. If your definition is more complex, you might need to build more complex logic within Zapier or use a webhook to a custom script that checks your conditions before deciding to create a ticket.

Here is a simplified example of what a Zap might look like:

1. Trigger: Set the trigger as the event that starts the Zap, like receiving a form submission.
2. Action (Search): Use a "Find User" action in Zendesk to search for the user by email.
3. Filter: Set up a Filter that only continues if the "Find User" action did not find an existing user.
4. Action (Create Ticket): If the Filter passes, create a new ticket in Zendesk.

Remember, Zapier's capabilities and the logic you can build with filters and paths can become quite complex, and you should test your setup thoroughly to ensure it behaves as expected. If your requirements are very specific and cannot be met by Zapier's built-in functionality, you might need to use a custom Zapier Webhook to interact with an external service that runs more sophisticated logic.  Hope this helps!

Brandon