Create a Salesforce contact from a Gravity Forms form submission (with a ZeroBounce email address validation)
Create a Salesforce contact from a Gravity Forms form submission (with a ZeroBounce email address validation)
Apps used in template
About
Use this template to automatically create a Salesforce contact when a Gravity Forms form is submitted. The Salesforce contact is created only if the email address submitted in the Gravity Forms form is valid (email validation is done using ZeroBounce).
Your Gravity Forms form has to include an 'Email' and a 'Last name' fields (fields that are not required but you can include them are: First name, Phone, Street address, City, Postal code, State/province, Country).
Trusted by thousands of fast-scaling organizations around the globe
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create your own workflow
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Completes or aborts a job.
Creates a new bulk data job.
Creates a new record in an object.
Deletes a record.
Downloads an attachment or a document.
Gets usage of API.
Shows credits you have left on your account.
Aggregates results (entry counts) of a form.
Gets the details of a form based on the specified form ID.
FAQ
Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.
A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.
Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.
Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.
How it works
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.










