I have a question regarding Capsule CRM and Zapier posibilities. I have a google form where input will be added to CapsuleCRM. But some organisations I work with have one email address used by the whole team (but different first and last names in google form).
So now, Zapier only checks on email in my case (most safe usually). How to overcome that a new contact with same email address will not be seen as an already existing contact?
I have attached the action.
Hope some of you recognize my issue!
Thanks in advance for your support!
Best answer by Troy TessaloneView original
You may have to add some conditional logic to your Zap such as this…
If Find Contact = TRUE, then compare the First Name and Last Name
If Name does not match, then Create Contact in Capsule.
Thank you for your quick reply. Where can I find conditional logic? and where would I need to add it (within the action?).
Thanks again! much appreciated!
You’d have to define the conditional logic then structure your Zap in a way to handles the different use cases.
Some Zap app options include…
Formatter > Math > Perform Spreadsheet Style Formula
NOTE: It may take a few of these apps to achieve these desired conditional logic within your Zap(s).
Thank you for your options.
Since Im a beginner with Zapier I would like to ask what conditions would suit my case?
Google form retrieves email address and first and last name into row of spreadsheet. Then within Capsule I check if email already exists → then no new contact. But in this case the team of the organisation uses one e-mail address for all team members. So I need to let capsule know that when email address exists, but when with a name in row of spreadsheet which does not exist, then new contact.
...well...if you have some ideas how to tackle this one, I have tried filter/paths/formatter (coding will not be a succes!) but I dont see an option to make the condition to check on email address AND name.
Might be best to start by listing out your different use cases that Zaps will need to handle with conditional logic.
You can try structuring this via nested Paths.
PS, I found an addendum :)
Choose false if you want subsequent steps to always be skipped when nothing is found. This is the most common case. The true option is used for greater control with filters and paths. If true, we will consider a "not found" result from this search step as a "success" and will always run subsequent Filter or Paths steps, allowing them to branch on whether or not the search returned a result.
So is my thinking correct: so first find emailaddress, then (path step) check again for name and if not true then add contact…?
I'll spend another day at soon! Thanks Troy. Much appreciated!
Hope I'll get the hang of this Zapier zapping :) its brilliant...once you get it ;)