SIGAVI 360 Integration — Missions and Leads

The SIGAVI 360 integration connects your SIGAVI to Play2sell for two things:

Missions — activities, visits, and events that brokers record in SIGAVI count toward the gamification missions.
Leads — each SIGAVI service record (FAC) becomes a lead in Play2sell, with the responsible broker and the funnel stage.

Setup is done screen by screen, with no coding, and takes about 10 minutes.

SIGAVI is the source of truth. Play2sell only reads your SIGAVI — nothing is created, changed, or deleted there. The read happens every 10 minutes: what the broker records in SIGAVI appears in Play2sell within 10 minutes.

What you’ll set up

Step	What you do	Result
1	Get the integration user from your SIGAVI	the connection’s read credential
2	Connect SIGAVI in the Play2sell panel	access checked on the spot
3	Choose what to turn on and the stage for each situation	missions and leads synchronized
4	Check the first read	integration validated

Prerequisites

Be an administrator of the company in Play2sell (only administrators turn the integration on or off).
Have your SIGAVI’s integration user — it is the API user, not your personal login.
The brokers registered in Play2sell with the same email (or the same CPF/CNPJ) they have in SIGAVI.

How does the integration work?

The broker works in SIGAVI

They record activities, visits, and service records as they always have.

Play2sell reads what changed

Every 10 minutes Play2sell queries your SIGAVI and brings in what was created or changed since the previous read. Each read steps back a few minutes over the previous one, so as not to miss anything that was saved along the way — whatever comes in repeated is recognized and does not count twice.

Activities count toward missions

Each activity, visit, or event is attributed to the broker who recorded it and becomes available to your company’s missions.

Records become leads

Each service record becomes a lead. When the record changes situation in SIGAVI, the lead follows, moving to the funnel stage you chose.

How the broker is identified

Record	How Play2sell finds the broker
Activities, visits, and events (missions)	by the broker’s email in SIGAVI; if not found, by their CPF/CNPJ in SIGAVI
Service record (lead’s responsible broker)	by the broker’s email in SIGAVI

A record whose broker is not found generates no points, and the lead is left without a responsible broker. To avoid this, keep the brokers’ email and CPF the same in both systems.

If the same person is registered twice in Play2sell (once with the email, once with the CPF), the record goes to the registration found by email. It is worth merging duplicate registrations before connecting.

Step 1 — Get the integration user in SIGAVI

The connection needs three values: address, integration user, and password.

Open your SIGAVI's API help

With your administrator login, go to yourcompany.sigavi360.com.br/Help (replace yourcompany with your SIGAVI’s address).

View the integration credential

On the help page, use the option to view the integration user and password and copy both values.

Note the address

It is the part before .sigavi360.com.br — in yourcompany.sigavi360.com.br, the address is yourcompany.

You have address, integration user, and password in hand.

The integration password is sensitive — treat it like any password. In Play2sell it is stored and never shown again. If you can’t find the integration credential in the SIGAVI help, ask SIGAVI support for your company’s API user.

Step 2 — Connect in the Play2sell panel

In the Play2sell panel, go to Integrações → Conectores (Integrations → Connectors), find SIGAVI 360, and click Conectar (Connect).

Field	What to enter
Endereço do SIGAVI (SIGAVI address)	The part before `.sigavi360.com.br` (e.g., `yourcompany`). If you paste the full address, the panel uses only that part.
Usuário de integração (Integration user)	The API user copied in Step 1.
Senha (Password)	The integration password.

When you click Continuar (Continue), Play2sell checks the access on the spot in your SIGAVI. If the user or the password doesn’t get in, you see the reason right there and nothing is saved.

Step 3 — Choose what to turn on

After checking the access, the panel shows what can be turned on:

Option	What it does
Missões (Missions)	Brokers’ activities, visits, and events in SIGAVI count toward missions.
Leads	Each SIGAVI service record becomes a lead, with the responsible broker.

You can turn on both or just one.

Funnel stage for each situation

With Leads turned on, the panel lists your SIGAVI’s service situations — read from your account, with the names your company uses — and, next to each one, the stages of your lead funnel in Play2sell.

When there is a stage with the same name as the situation, it comes already selected.
For the others, choose the stage — or leave “Manter a etapa em que o lead está” (Keep the stage the lead is in).

Record’s situation in SIGAVI	What happens to the lead
Has a stage chosen	The lead goes to that stage whenever the record is in that situation.
”Manter a etapa em que o lead está”	A new lead enters the first stage of the funnel; a lead that already exists stays where it is.

Click Conectar. The first read goes out within 10 minutes.

You don’t need to map everything at once. You can come back later, in Editar configuração (Edit configuration), and adjust the stages — the choices already made come filled in.

Step 4 — Check the first read

Wait up to 10 minutes

The first read brings in the records changed in the last 24 hours and the activities from the last 2 hours. Anything older than that is not imported.

Check a lead

Open the lead funnel and look for a recent service record from SIGAVI: name, contact, responsible broker, and stage should match.

Check an activity

Ask a broker to record an activity in SIGAVI and, after 10 minutes, see their progress in the missions.

What is read from SIGAVI

From SIGAVI	Becomes in Play2sell	Note
Service record (FAC)	Lead	Customer’s name, email, and phone, responsible broker, and situation. One record, one lead.
Record registered	Event for the missions	Counts once per record, at the moment of registration. It carries neither the customer’s name nor contact.
Record activities	Events for the missions	Attributed to the activity’s broker.
Visits	Events for the missions	Attributed to the visit’s broker.
Record events	Events for the missions	Attributed to the event’s broker.

Lead rules

One record, one lead. If the same record is read again, the lead is updated — it is not duplicated.
Name and contact come from SIGAVI. A field that arrives empty from SIGAVI does not erase what is already on the lead.
What you enriched in Play2sell stays. Amount, document, and other data filled in within Play2sell are not overwritten by the read.
Deletions are not mirrored. A record deleted in SIGAVI remains as a lead in Play2sell.

Edit or turn off

In Integrações → Conectores → SIGAVI 360 → Editar configuração:

Review the configuration: enter the integration password again (it is not visible after being saved), adjust whatever you want, and save.
Desligar integração (Turn off integration): the reads stop. Leads and points that have already come in remain in Play2sell, and you can turn it on again whenever you want — the read resumes from where it stopped.

Frequently asked questions

How long does it take for what I do in SIGAVI to appear in Play2sell?

Within 10 minutes. SIGAVI does not notify when something changes, so Play2sell queries every 10 minutes.

Does Play2sell change anything in my SIGAVI?

No. The integration is read-only.

I moved the lead to another stage in Play2sell. Will the read undo it?

Only if the record’s situation in SIGAVI has a stage chosen in the mapping — in that case SIGAVI rules. If the situation is set to “Manter a etapa em que o lead está”, the lead stays where you put it.

We created a new situation in SIGAVI. What now?

Records in that situation keep becoming leads, and the lead stays in the stage it is in. To direct it to a stage, open Editar configuração: the new situation appears in the list.

Do the brokers' old activities come in?

No. The integration starts counting from the connection (with the windows from Step 4).

Can the same activity count twice?

No. Each SIGAVI record has its own identification; what is read again is recognized and ignored.

What about commission payments (Pagadoria)?

It is not yet available for SIGAVI. This integration covers Missions and Leads.

Troubleshooting

What appears	Likely cause	What to do
”O SIGAVI recusou o usuário ou a senha.” (SIGAVI rejected the user or the password.)	Incorrect integration user or password, or the personal login was used.	Copy the integration credential again from the SIGAVI API help (Step 1).
”O SIGAVI aceitou o usuário, mas não deixou ler os dados.” (SIGAVI accepted the user, but did not allow reading the data.)	The user entered is not the integration one.	Use the API user, not the personal login.
”Endereço do SIGAVI inválido.” (Invalid SIGAVI address.)	Something beyond your company’s address was entered.	Enter only the part before `.sigavi360.com.br`.
”Resposta inesperada do SIGAVI…” (Unexpected response from SIGAVI…)	Your SIGAVI’s API is down or returning an error.	Try again in a few minutes. If it persists, ask SIGAVI support to check your company’s API.
”Há situações em etapas que não são do funil de leads desta empresa.” (There are situations in stages that do not belong to this company’s lead funnel.)	A funnel stage was removed while the screen was open.	Close and open the configuration again and redo the choice.
Lead without a responsible broker	The record’s broker was not found in Play2sell.	Check whether the broker’s email is the same in both systems.
Activity did not count toward the mission	The broker was not found, or there is no mission that counts that type of activity.	Check the broker’s registration and the company’s active missions.

Reference

Item	Value
Direction	SIGAVI → Play2sell (read-only)
Frequency	every 10 minutes
First read	records from the last 24 hours; activities from the last 2 hours
Broker identity	email; for activities, in the absence of the email, CPF/CNPJ
Lead identity	the record’s internal number in SIGAVI
Who can configure	company administrators

​What you’ll set up

​How does the integration work?

​How the broker is identified

​Step 1 — Get the integration user in SIGAVI

​Step 2 — Connect in the Play2sell panel

​Step 3 — Choose what to turn on

​Funnel stage for each situation

​Step 4 — Check the first read

​What is read from SIGAVI

​Lead rules

​Edit or turn off

​Frequently asked questions

​Troubleshooting

​Reference

What you’ll set up

How does the integration work?

How the broker is identified

Step 1 — Get the integration user in SIGAVI

Step 2 — Connect in the Play2sell panel

Step 3 — Choose what to turn on

Funnel stage for each situation

Step 4 — Check the first read

What is read from SIGAVI

Lead rules

Edit or turn off

Frequently asked questions

Troubleshooting

Reference