Automate Sympla with Nibo
Unlock the superpowers of Sympla + Nibo and automate your tasks without having to write a single line of code.
Sympla and Nibo
your way
Check out the available triggers and actions in the automation of apps Sympla + Nibo
Approved participant
For each new participant with “approved” status on a Sympla eventHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved participant
For each new participant with “approved” status on a Sympla eventTrigger
Participant identifier
Order Identifier
ID do evento
First name
Last name
Ticket name
Ticket number
Ticket price
Request Date
Order discount
Order update date
Order approval date
UTM source
UTM medium
UTM campaign
UTM term
UTM content
Cancelled/refunded order
For each new cancelled/refunded order on SymplaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cancelled/refunded order
For each new cancelled/refunded order on SymplaTrigger
Order identifier
Total order amount
Buyer's first name
Buyer's last name
Buyer's email
Event ID
Request Date
Order update date
Order status
Discount Code
[Invoice] Address: city
[Invoice] Address: state
[Invoice] Address: neighborhood
[Invoice] Address: street
[Invoice] Address: 2nd street
[Invoice] Address: no.
[Invoice] Address: Zip Code
[Invoice] Document No.
[Invoice] Document type
Transaction type
Full name of participants separated by comma
participant email separated by comma
Event's start date
Event's end date
Event name
Event's description
Event logo
Event URL
Event adress house name
Event adress street name
Event adress house number
Event adress house complement
Event adress neighbourhood
Event address city
Event address state code
Event address ZIP Code
Event address country
Event address latitude
Event address longitude
Participant check-in
When check-in for a participant is completed on a Sympla eventHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Participant check-in
When check-in for a participant is completed on a Sympla eventTrigger
Participant identifier
Order Identifier
First name
Last name
Ticket name
Ticket number
Ticket price
Created order
For each created order on SymplaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created order
For each created order on SymplaTrigger
Order identifier
Total order amount
Buyer's first name
Buyer's last name
Buyer's email
Event ID
Request Date
Order update date
Order status
Discount Code
[Invoice] Address: city
[Invoice] Address: state
[Invoice] Address: neighborhood
[Invoice] Address: street
[Invoice] Address: 2nd street
[Invoice] Address: no.
[Invoice] Address: Zip Code
[Invoice] Document No.
[Invoice] Document type
Transaction type
Full name of participants separated by comma
participant email separated by comma
Event's start date
Event's end date
Event name
Event's description
Event logo
Event URL
Event adress house name
Event adress street name
Event adress house number
Event adress house complement
Event adress neighbourhood
Event address city
Event address state code
Event address ZIP Code
Event address country
Event address latitude
Event address longitude
Refused order
For each new declined order on SymplaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refused order
For each new declined order on SymplaTrigger
Order identifier
Total order amount
Buyer's first name
Buyer's last name
Buyer's email
Event ID
Request Date
Order update date
Order status
Discount Code
[Invoice] Address: city
[Invoice] Address: state
[Invoice] Address: neighborhood
[Invoice] Address: street
[Invoice] Address: 2nd street
[Invoice] Address: no.
[Invoice] Address: Zip Code
[Invoice] Document No.
[Invoice] Document type
Transaction type
Event's start date
Event's end date
Event name
Event's description
Event logo
Event URL
Event adress house name
Event adress street name
Event adress house number
Event adress house complement
Event adress neighbourhood
Event address city
Event address state code
Event address ZIP Code
Event address country
Event address latitude
Event address longitude
Approved order
For each new approved order on SymplaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved order
For each new approved order on SymplaTrigger
Order identifier
Total order amount
Buyer's first name
Buyer's last name
Buyer's email
Event ID
Request Date
Order update date
Order approval date
Order status
Discount Code
[Invoice] Address: city
[Invoice] Address: state
[Invoice] Address: neighborhood
[Invoice] Address: street
[Invoice] Address: 2nd street
[Invoice] Address: no.
[Invoice] Address: Zip Code
[Invoice] Customer name
[Invoice] Document No.
[Invoice] Document type
Transaction type
Full name of participants separated by comma
participant email separated by comma
Event's start date
Event's end date
Event name
Event's description
Event logo
Event URL
Event adress house name
Event adress street name
Event adress house number
Event adress house complement
Event adress neighbourhood
Event address city
Event address state code
Event address ZIP Code
Event address country
Event address latitude
Event address longitude
Expired order
For each new expired order on SymplaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Expired order
For each new expired order on SymplaTrigger
Order identifier
Total order amount
Buyer's first name
Buyer's last name
Buyer's email
Event ID
Request Date
Order update date
Order status
Discount Code
[Invoice] Address: city
[Invoice] Address: state
[Invoice] Address: neighborhood
[Invoice] Address: street
[Invoice] Address: 2nd street
[Invoice] Address: no.
[Invoice] Address: Zip Code
[Invoice] Document No.
[Invoice] Document type
Transaction type
Event's start date
Event's end date
Event name
Event's description
Event logo
Event URL
Event adress house name
Event adress street name
Event adress house number
Event adress house complement
Event adress neighbourhood
Event address city
Event address state code
Event address ZIP Code
Event address country
Event address latitude
Event address longitude
Generate account receivable
generate an account receivable on NiboHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate account receivable
generate an account receivable on NiboAction
Company Required
description Required
reference
Amount Required
Scheduling Required
Due date Required
Category Required
Cost center selection
Cost center id
Cost center description
Number of installments
Customer name. Required
Customer email.
Customer Document Number.
Customer phone number.
Customer's cell phone.
Customer address
Customer address number
Customer address complement
Customer address neighborhood
City of customer address
Customer address state
Customer address Zip Code
Country of customer address
Include expense
include an expense on NiboHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Include expense
include an expense on NiboAction
Company Required
Account Required
Category Required
Cost center selection
Cost Centers
Cost center description
Amount Required
Entry date Required
description Required
Provider's name. Required
Supplier email.
Supplier Document Number.
Supplier's telephone number.
Supplier's cell phone.
Supplier address
Supplier address number
Supplier address supplement
Supplier address neighborhood
City of supplier address
Supplier address state
Supplier address Zip Code
Country of supplier address
Register customer
register the customer on NiboHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Register customer
register the customer on NiboAction
Company Required
Name Required
Document
Customer phone number.
Customer's cell phone.
Customer address
Customer address number
Customer address complement
Customer address neighborhood
City of customer address
Customer address state
Customer address Zip Code
Country of customer address
Register vendor
register the vendor on NiboHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Register vendor
register the vendor on NiboAction
Company Required
Name Required
Document
Customer phone number.
Customer's cell phone.
Customer address
Customer address number
Customer address complement
Customer address neighborhood
City of customer address
Customer address state
Customer address Zip Code
Country of customer address
Include receipt
include a receipt on NiboHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Include receipt
include a receipt on NiboAction
Company Required
Account Required
Category Required
Cost center selection
Cost Centers
value
Amount Required
Entry date Required
description Required
Customer name. Required
Customer email.
Customer Document Number.
Customer phone number.
Customer's cell phone.
Customer address
Customer address number
Customer address complement
Customer address neighborhood
City of customer address
Customer address state
Customer address Zip Code
Country of customer address
Didn't find your use case? Send suggestion.
Automate Sympla and Nibo with Pluga integrations
Explore automation templates
For each new approved order on Sympla, include a receipt on Nibo
EXPLORE Miss an automation with this apps?
Say to us!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 Sympla + Nibo
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. 
Sympla
EventSympla is an event management and creation platform. The app offers solutions for organizing, selling tickets, managing participants, and promoting online and in-person events. It is one of the well-known platforms in the Brazilian market, reaching all types of events and audiences.
Integrations with Sympla Visit Sympla Nibo
AccountingNibo is a simple robust financial management system for small and medium-sized businesses. Among other features, the platform allows the unification of accounting file formats and their sharing between the company and the accountant, acting as an intermediary to save you time. This way, every manager can have their finances and accounting online, organized, and efficient.
Integrations with Nibo Visit Nibo