Before you start
You need a JobDiva admin who can add users, and someone who can contact JobDiva support for your company. JobDiva doesn't sell API access as a separate self-serve setting, so the client ID comes from JobDiva.
You will paste three things into Metaintro:
Your API client ID, which JobDiva support gives your company.
The email address of the JobDiva user Metaintro signs in as.
That user's password.
We suggest a dedicated JobDiva user for Metaintro, so the connection keeps working when staff change.
Create the credential in JobDiva
JobDiva's public API reference doesn't name the menus for creating an API user or a client ID, so we won't guess at them here. In general:
Ask JobDiva support for an API client ID for your company, and say you're connecting Metaintro.
In JobDiva, create a user for Metaintro, or choose the user you want Metaintro to sign in as. Ask your JobDiva admin or JobDiva support if you're not sure where to add users.
Note that user's email address and password.
JobDiva's API reference: JobDiva API.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose JobDiva.
In API client ID, enter the client ID from JobDiva support. It is a number.
In API user email, enter the email the JobDiva user signs in with.
In API user password, enter that user's password.
Select Connect.
Metaintro checks the details by signing in and reading one job. Then map your JobDiva 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 as a candidate with their name, and their email and cell phone when they shared them.
Applies them to the matching JobDiva job.
Uploads their résumé when they shared one.
Adds a note on the candidate, linked to the job, with a link to their proof card and their short summary when they wrote one.
Candidates, applications and résumés are tagged with a résumé source named Metaintro, which Metaintro adds to your JobDiva résumé sources.
If a JobDiva candidate already has the same email, as their main or alternate email, Metaintro applies that candidate to the job instead of creating a new one.
JobDiva doesn't send hiring updates to other apps, so Metaintro checks each shared candidate regularly. It reads the status of the latest submittal for that candidate on that job. Statuses named like Hired or Placed show as hired, names like Rejected show as not selected, and names like Withdrawn show as withdrawn. Until you create a submittal, the candidate shows as applied.
Limits
Stage updates are not instant. Metaintro checks for changes on a schedule.
Metaintro can't move candidates between stages in JobDiva. Move them in JobDiva.
Metaintro reads submittal status names. A name it doesn't recognize shows as still in progress.
Metaintro matches an existing candidate by exact email. A person who shared no email can't be matched, so Metaintro creates a new candidate for them. If 20 or more JobDiva candidates come back for one email, Metaintro stops rather than guess.
The connection signs in as a JobDiva user. If that user's password changes or the user is turned off, the connection stops working until you reconnect.
JobDiva doesn't publish a request limit. If JobDiva slows Metaintro down, Metaintro waits and tries again.
If something goes wrong
Sign-in rejected. Check the client ID, email and password. If the password changed, connect again with the new one. If the client ID was never issued for API use, ask JobDiva support.
Missing permission. JobDiva refused an action for that user. Ask your JobDiva admin to give the user access to candidates and jobs, or ask JobDiva support which access API users need.
Rate limited. Metaintro pauses and tries again later. You don't need to do anything.
A candidate didn't arrive. Check that the job is still mapped and open in JobDiva, then look for the candidate by email in JobDiva.