Automate Zendesk with Meets
Unlock the superpowers of Zendesk + Meets and automate your tasks without having to write a single line of code.
Zendesk and Meets
your way
Check out the available triggers and actions in the automation of apps Zendesk + Meets
New created user
For each new user created on ZendeskHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
New created user
For each new user created on ZendeskTrigger
Name
Telephone
Location
User Tags
Creation date/time
User organization
Opportunity reaches stage in the sales pipeline
When an opportunity reaches a certain funnel stage on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity reaches stage in the sales pipeline
When an opportunity reaches a certain funnel stage on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Ticket inserted into a view
When a new ticket is inserted in a certain view on ZendeskHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Ticket inserted into a view
When a new ticket is inserted in a certain view on ZendeskTrigger
id
Type
Subject
Description
Priority
Status
Tags
Creation date
Creation time
Requestor Name
Applicant Email
Requesting telephone number
Requesting Location
Name Organization
Name of assignee
Lost opportunity
For each lost opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost opportunity
For each lost opportunity on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Won opportunity
For each conquered opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won opportunity
For each conquered opportunity on MeetsTrigger
Opportunity ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Created opportunity
For each created opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created opportunity
For each created opportunity on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
RESPONSIBLE USER
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Create ticket
create a ticket on ZendeskHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create ticket
create a ticket on ZendeskAction
subject Required
Applicant's name Required
Requestor's email Required
Applicant's telephone number
description Required
Ticket Tags
Assigned
Select type
Select priority
Select status
Add or update opportunity
register an opportunity on MeetsHow it works:
Whenever something happens on the source app
1. An deal will be added/updated on Meets
2. A person associated with this deal will be created/updated on Meets
All happening in a single automation! ✨
Add or update opportunity
register an opportunity on MeetsAction
Opportunity Title Required
Opportunity Tag/Status
Responsible Required
Amount
Products/Services
Name/Corporate Name
Kind of person Required
CPF
CNPJ
Cell phone
Telephone
Occupation area
Origin
City
State
Didn't find your use case? Send suggestion.
Automate Zendesk and Meets with Pluga integrations
Explore automation templates
Trusted by over 10.000 amazing companies
How to integrate apps with Pluga?
Pluga allows you to integrate two or more apps in a simple, practical way without needing to type a single line of code. Here are the steps to automate your tasks and start focusing on what really matters.
-
What is the automation trigger?
The trigger is the step that initiates automation. In the integration process, it is selected after choosing the source app. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.
-
What is an action within an automation?
The action serves as a response to the previously selected trigger. That is, it occurs once the trigger is activated. For example, in an automation between Facebook Lead Ads (source) and Google Sheets (destination), as soon as the trigger “For each response on an advertisement” is activated in the source app, the action “Add data to a new row on a spreadsheet” will be carried out in the destination app.
-
How does information mapping work?
Information mapping is where you configure which captured information from the source app will be sent to each field in the destination app(s).
For example, in an automation between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.
-
Is it possible to have more than one action?
With Pluga, you can create automations by integrating several apps at once. For example, you can integrate Facebook Lead Ads + Google Sheets + Slack, so when the trigger is activated, the first action is executed and a notification is sent via Slack.
Automate Zendesk + Meets
and say goodbye to manual (and tedious) tasks!
By connecting the apps you use through Pluga, you can automate various processes in your routine and have time for tasks that really matter. 
Zendesk
SupportZendesk is a customer support and service platform. This app provides features to manage support tickets, offer multichannel support, automate responses, and analyze support performance.
Integrations with Zendesk Visit Zendesk Meets
CRMMeets is a CRM platform designed to simplify and streamline contact management. The app allows you to visualize your entire sales process, tracking the right activities to be performed.
Integrations with Meets Visit Meets