ABC Evo (EVO / W12 - Gyms)
ABC Evo is the NicoApp that integrates with the EVO (W12) system, used by gyms. With it, your flow looks up and registers students and opportunities and schedules trial classes.
Note
Available in the NicoApps tab. The integration is based on the official EVO API (evo-integracao.w12app.com.br).
Requirements and limits (EVO API plans)
Attention
The EVO API is available only to customers on the EVO Black plan. Without EVO Black, there is no way to use this NicoApp. Within EVO Black there are two API plans, with very different limits:
Plan
Cost
Limits
Notes
API Plus
Included in the EVO Black monthly fee
1,000 requests/month and up to 100 requests/day. When the limit is reached, new requests are blocked until the period renews.
Suitable for testing and very low volumes.
API Pro
R$ 39,90/month + R$ 2,72 per 100 daytime requests (6h–23h59) or R$ 1,36 per 100 nighttime requests (0h–5h59)
Unlimited daily queries (billed by actual usage); higher requests-per-minute limit.
Includes Webhook, exclusive workshops and priority access to new features. Billing is due on the 15th.
Note
Mind the sizing: a support flow consumes several requests per conversation (search for the opportunity, list activities, check available times, schedule...). With the API Plus limit of 100/day, a few conversations a day already exhaust the quota — for real automation, the recommended plan is API Pro.
Authentication
EVO uses Basic Auth with two credentials, which you provide when installing the app:
- Gym DNS — your gym's identifier in EVO (the API user).
- Secret Key (Token) — the password generated together with the token.
To generate the credentials in the EVO panel:
- Go to Configuração → Integrações → card EVO API.
- Click NOVO TOKEN and confirm your EVO login and password.
- Fill in the three sections: Geral (token name, requester and WhatsApp), Utilização (purpose of the integration) and Permissões — check the access to the endpoints the app uses: members, prospects (opportunities), activities/schedule, sales, services and settings.
- Accept the terms of use. The panel will show the DNS (user) and the Token (password) — copy and paste them into the NicoApp fields.
- Validity: tokens you create are valid for 2 years (EVO notifies you 30 days before they expire). Tokens generated by support expire in 3 days.
- Single-unit vs. multi-unit key: the single-unit key accesses the data of one unit; the multi-unit key accesses several (by specifying the branch). If your gym has several units, generate the multi-unit key and use the Branch ID field in the app's actions.
- Management: in the Tokens tab of the EVO panel you can activate/deactivate, edit permissions and delete keys; in the Consumo tab, track the requests per month and per token.
Attention
The credential is validated on the first action executed. If an action fails with an authorization error, check the DNS and the Token in the app settings — and whether the token's Permissões cover the endpoint used by the action.
Available actions
01 Members
Action
What it does
Main inputs
Outputs
Search for Members
Searches students by name, e-mail or phone
Name, E-mail, Phone (at least one)
Members Found (JSON), Total Found
Create Student (Member)
Registers a new student in EVO
Branch, Name (required); Last Name, E-mail, Mobile, CPF, Date of Birth, Gender
Student ID (idMember)
02 Opportunities
Action
What it does
Main inputs
Outputs
Search for Opportunity
Searches prospects by name, e-mail, phone or CPF
Name, E-mail, Phone, CPF (at least one)
Opportunities Found (JSON), Total Found
Create Opportunity
Creates a prospect in EVO
Name (required); Last Name, E-mail, Mobile, Gender, Funnel Stage, CPF
Opportunity Id (idProspect)
Update Opportunity
Updates the data of an existing prospect
Opportunity Id (required) + fields to update (includes Date of Birth and Notes)
Opportunity Id
03 Sale and Scheduling
Action
What it does
Main inputs
Outputs
Check Available Times
Lists activity times with openings on a given date (occupancy < capacity)
Date (YYYY-MM-DD); Activity IDs (optional)
Available Times (JSON), Total Found
Schedule Services
Enrolls the opportunity in an activity time slot
Configuration ID, Activity Date, Opportunity Id
—
Create Sale
Creates a sale for the opportunity (payment pending; no card)
Branch, Service, Opportunity Id
Sale ID (idVenda)
Create Sale and Book
Creates the sale and already enrolls in the chosen time slot
Branch, Service, Opportunity Id, Configuration ID, Activity Date
Sale ID
Schedule Trial Class
Schedules a trial class for the opportunity (dedicated EVO endpoint)
Opportunity Id, Date/Time, Activity Name, Service Name; idActivity/idService/Branch (optional)
—
Check Contact Appointments
Lists the scheduled sessions of an opportunity or student (confirmations and reminders)
Opportunity Id or Student ID; optional period
Appointments Found (JSON), Total Found
Change Appointment Status
Marks Present, Absent or Excused Absence on the session
Status, Configuration ID, Activity Date, Opportunity Id or Student ID
—
04 Catalog and Configuration
Action
What it does
Main inputs
Outputs
Check Services
Lists the registered services (filter by name)
Name (optional)
Services Found (JSON), Total Found
Check Units
Lists the gym's units/branches
Branch ID (optional, filters one unit)
Units Found (JSON), Total Found
Check Activities
Lists the gym's activities (classes)
Name (optional), Branch (optional)
Activities Found (JSON), Total Found
Check Available Times (AI)
Version for the AI Agent: returns the unique times with openings already in function format (role/name/content)
Date; Activity IDs (optional)
AI Response
Recommended flow: automated trial class
- Lead arrives on WhatsApp → Search for Opportunity (by phone) → if it does not exist, Create Opportunity.
- Check Activities → the flow presents the available classes.
- Check Available Times (in the AI Agent, use the AI version as a function).
- Schedule Trial Class with the chosen time.
- Pre-class reminder (sequence) using Check Contact Appointments.
- After the class: Change Appointment Status → Present triggers the offer; Absent triggers the rescheduling sequence.
- Plan closed: Create Sale (or Create Sale and Book) — the sale converts the opportunity into a student in EVO. For direct registration, use Create Student (Member).
Tips and notes
- Save requests: keep the limits of your API plan in mind. Avoid querying the catalog (activities/services/units) on every message — this data rarely changes; store the IDs in flow variables or use the app's dynamic selects (chosen once, when designing the flow).
- Date formats: plain dates in
YYYY-MM-DD(e.g. 2026-08-01); activity date/time inYYYY-MM-DDTHH:MM:SS(e.g. 2026-08-01T10:00:00). - Error handling: when EVO refuses an operation (e.g. time slot full, request limit reached), the action fails and returns EVO's real error message — use the block's error path to handle it in the flow.
- Chained IDs: the Opportunity Id comes out of Create/Search Opportunity and goes into Update, Schedule, Trial Class and Sales. The Configuration ID + Activity Date identify the time slot and come out of Check Available Times.
- Dynamic selects: the Branch, Service and Activity fields load their options directly from your EVO account (after installing with the credentials). Fields that vary per contact (name, CPF, opportunity id…) accept flow variables.
- Payment: Create Sale records the sale with payment pending (payment 2); card charging is not performed by the app in this version.