Before you start
You need a Gupy user with the master or administrator profile, and that profile needs permission to manage public API tokens. If you don't see the option to create a token, contact Gupy support.
You will paste one thing into Metaintro: a Gupy API token. Gupy tokens don't expire.
Create the credential in Gupy
Sign in to Gupy Recrutamento & Seleção as a master or administrator user.
Open SETUP > Configurações Avançadas > Geração de Tokens.
Select Gerar Token.
Give the token access to these endpoints: career pages, jobs, steps, applications, comments and tags. Metaintro needs all of them.
Copy the token.
Gupy's guides: Authentication for Recruitment & Selection and How to enable the public API token.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Gupy.
In API token, paste the token you copied.
Select Connect.
Metaintro checks the token by reading your career pages. Then map your Gupy jobs to your Metaintro jobs, set your rules, preview, and go live.
What Metaintro sends and reads
Metaintro only sends people who chose to share their profile with you for that job. For each person, Metaintro:
Adds them to the matching Gupy job with their name, email and phone when they shared one. The insertion source is set to market referral or consulting.
Tags the application Metaintro.
Adds a comment to the application with a link to their proof card, plus their short summary when they wrote one. When they shared a résumé, it is attached to that comment.
Gupy recognizes people by email. If the person is already in Gupy, Metaintro uses their existing record. If they already applied to that job, Metaintro adds its tag and comment to that application instead of creating a new one.
Gupy doesn't send hiring updates to Metaintro, so Metaintro checks each shared candidate's application regularly. Hired, reproved and gave-up applications show in Metaintro as hired, not selected and withdrawn. For candidates still in process, Metaintro reads the step name and category, such as interview or offer.
When you move a candidate from Metaintro, it moves the Gupy application to a step that matches the stage, such as an interview or offer step. Marking someone not selected reproves them in Gupy with the reason Other.
Limits
The résumé is attached to the Metaintro comment, not to the candidate's résumé field. Gupy fills that field only through quick apply, which needs the person's CPF.
Metaintro doesn't send Gupy's invitation to complete the application. Your team can invite the candidate from Gupy if your process needs it.
Hires and withdrawals can't be set from Metaintro. Make those changes in Gupy.
Stage updates are not instant. Metaintro checks for changes on a schedule.
Metaintro looks through up to 1,000 applications on a job to find an existing candidate. On a job with more applications than that, it stops rather than risk a duplicate.
Gupy limits API traffic to about 500 requests per minute. Metaintro paces its requests and waits when Gupy asks it to slow down.
If something goes wrong
The token is rejected. Check that you copied the whole token with no extra spaces, then try again. If it still fails, generate a new token.
Gupy says no company is associated to the token. The token doesn't have access to one of the endpoints Metaintro uses. Generate a new token with career pages, jobs, steps, applications, comments and tags enabled, then reconnect.
You can't find Geração de Tokens. Your profile needs the master or administrator role with permission to manage public API tokens. Ask a Gupy administrator, or contact Gupy support.
Metaintro is rate limited. Gupy asked Metaintro to slow down. Metaintro waits and tries again, so you don't need to do anything.
A move from Metaintro does nothing. The job may have no step that matches the stage. Check the job's steps in Gupy.