How to integrate with Zapier
Connect your User.com app to any of Zapier's 3000 available apps
Zapier is an extremely useful and fun-to-use app. In this tutorial, we'll walk through the triggers and actions that our Zapier integration offers - you can always check our API docs too.
In this case, you will create a Zap that will create a new row in one of your Google spreadsheets once a new User.com user is created. Another way to use Zapier integrations is to trigger an event for a particular user or update his or her profile.
Before you start
Sign up for Zapier.
Make sure you have administrative rights to the User.com account. Only then you can grant Zapier access to the app.
If you want to send events using Zapier, make sure that the event and its attributes have already been created. If not, go to App Settings -> User data & events -> Events.
Triggers
The triggers available in User.com through Zapier allow you to start workflows based on specific events within the User.com platform.
Once you are logged in Zapier, click "+Create" and select "Zaps". When choosing the trigger, simply type in "User.com" and click on the system's icon that appears on the list of apps.
.
Choose the trigger you want to use
Then select a specific Action you'd wish to take - for example, you can connect your Google Sheets to add a new row each time a new user is created in your user.com application. 
Other available triggers in Zapier's user.com module:
New Company
This trigger will fire when a new company is created. It's useful for all kinds of "Zaps" including tasks of account executives. In the next steps, choose the connection with your app and the application you will track. The sample collected by Zapier will include all the standard attributes of the company. You will be able to use all the downloaded attributes in the action and filter steps of your app.
New event
This trigger will fire when a user performs a selected event. It's flexible because a given event can be generated at any point for any user using automation processes.
It triggers when a new custom event is recorded for a user. Custom events can be anything from a user completing a specific action on your website to reaching a milestone within your app. This trigger allows you to respond to these events in real-time, such as sending a congratulatory email or triggering a follow-up task.
In the next steps, choose the connection with your app, the application you will track, and the event that will trigger the Zap. The trigger will pass along all the standard attributes of the user as well as the attributes of the event. Then you will be able to use all the downloaded attributes in the action and filter steps of your app.
New Tag
Triggers when a new tag is added to a user in User.com. Tags are often used to segment users based on behaviour, preferences, or demographics. This trigger can automate actions like enrolling users in specific marketing campaigns or updating their status in other apps based on the tags they receive.
New Activity
Triggers when a new activity is recorded in your user.com application.
New Deal
Triggers when a new deal is created.
Actions
Actions enable you to automate a wide range of marketing, sales, and support activities within User.com, enhancing efficiency and ensuring a cohesive user experience across different platforms. To use these actions, you would set up a Zap in Zapier, choosing a trigger from User.com or another app, and then defining the User.com action you want to happen in response. Here are some common types of actions you might find:
Create/Update Company
This action requires at least one field: company name. If the system recognizes the name of the company or company ID provided in the form, it will update the existing one instead of creating a new one. You can include any standard or custom company attributes in the action form.
Create/Update user
This action requires at least one of two fields: ID or email. If you add a unique user ID that matches one of the users inside User.com, the existing user with that ID will be updated to include the fields that you've included in the action form. If you don't provide any info in a given field, the user will keep the old data. If you provide an email address that is already in the database, the system will match the data with the oldest user with that email.
If you provide both an email and a user ID and the ID is unique, a new user will be created even if other users with the same email already exist. If the ID is already in the database, the user with that ID will be assigned a new email address.
Create an event
Choose an app and the event that you want to generate - always choose the app before the event, otherwise it won't work. Remember that you can only generate events that already exist in your app (meaning they have been triggered at least once or they have been added in the app settings section of your app).
In the action form, describe the event and its parameters as well as the user who should receive this event.
When describing the event, you will be able to add any event attribute that has ever been used in any event (not only those that were used in this event).
When describing the user, as in the case of create/update user, you need to provide either the user ID or email. If you add a unique user ID which matches one of the users inside User.com, the existing user with that ID will get the event. If you provide an email address that is already in the database, the system will match the data with the oldest user with that email. If you include both an email and ID, and the ID is already in the database, the user with that ID will get the event.
Create/Update Activity
Creates new Activity instance or update if an instance with given custom_id exists.
Create/Update Deal
Creates new Deal or updates if an instance with a given custom_id exists.
Troubleshooting
If you want to generate events but can't find them on the list, make sure that you have created them in the app.
If your events are not correctly delivered, make sure the email address or ID match one of the users. It's best to use the create/update user action before generating an event action to make sure that the event goes through.
If you update contact and get a 404 error during testing, make sure that the example item Zapier is using to test the connection has the email field of some user in your database. Otherwise, User.com won't identify which user should be updated and which test was signalled as failed. The same rule applies to the event creation zap.
If your example can't be downloaded, make sure that you have at least one company/user/event/tag.