Bring Infima client, user, training, phishing, and risk data into ScalePad to keep client records current and support security-awareness planning.
Infima data flows into ScalePad in one direction: Infima to ScalePad. The integration is read-only.
|
Who can use this feature?
|
|
What you'll need:
|
What the integration does
The Infima integration supports:
- Client records.
- User and contact records.
- Security-awareness training data.
- Phishing results.
- Sent training and phishing emails.
- User risk data.
- Client curriculum data.
ScalePad uses Infima client and user data for contact synchronization. Security-awareness data is also collected for supported reporting and planning workflows.
Generate an Infima API key
For more information, see the Infima API reference and Infima API-key documentation.
- Sign in to the Infima Partner Dashboard.
- Open the API-key management area.
- Create or select an API key for ScalePad.
- Grant access to the clients whose data ScalePad should read.
- Generate the API key.
- Copy the API key and store it securely in an approved password manager.
Infima uses the X-API-Key request header for authentication. Enter only the raw API key when connecting the integration. Do not add Bearer, quotation marks, or extra spaces.
Connect Infima to ScalePad
- Log into the ScalePad Hub and click Integrations.
- Click + Add Integration.
- Search for and select Infima.
- Enter the Infima API key.
- Select Save or Save and sync now.
- Confirm that the integration status changes to Connected or Syncing.
Fields we are syncing data for
| Infima object | Infima field | Lifecycle Manager field or destination |
|---|---|---|
| Client | id |
Client external ID |
| Client | name |
Client name |
| User | id |
Contact identifier |
| User | client_id |
Contact-client association |
| User | first_name |
Contact first name |
| User | last_name |
Contact last name |
| User | email |
Contact email address |
| Client |
industry, external_id, created_at, updated_at, user counts, risk summaries, training summaries, phishing summaries, frameworks, and feature flags |
Security-awareness data |
| User |
department, job_title, manager_email, status, role, preferred_language, source, group details, risk details, training status, overdue count, and next-course details |
Security-awareness data |
| Client curriculum item | Course, audience, source, framework, status, dates, assignment counts, completion counts, and completion rate | Security-awareness data |
| User training result | User, course, status, source, framework, dates, score, and certificate URL | Security-awareness data |
| User phishing result | User, client, template, status, event timestamps, origin, and remediation status | Security-awareness data |
| Sent email | User, email type, subject, sender, sent date, and delivery details | Security-awareness data |
| User risk | Risk score, grade, baseline, role, risk tallies, risk factors, and calculated date | Security-awareness data |
How syncing works
| Behavior | Details |
|---|---|
| Initial sync | ScalePad verifies the API key, retrieves accessible Infima clients, retrieves users for each client, and collects supported security-awareness data. |
| Ongoing sync | [TODO: confirm the scheduled sync cadence or user-triggered sync behavior] |
| Matching | Clients use the Infima client ID. Users use the Infima user ID and are associated with the client returned by Infima. |
| Updates and overwrites | [TODO: confirm whether empty vendor values overwrite existing ScalePad values] |
| Deletes or archives | [TODO: confirm how inactive or deleted Infima clients and users are handled] |
| Failures and retries | Rate-limit responses are retried by the integration. Authentication and permission failures stop the affected operation and must be corrected before retrying. |
Troubleshooting
| Symptom or error | Likely cause | Resolution |
|---|---|---|
| The integration rejects the API key | The key is invalid, unavailable, or entered with extra text. | Generate or copy the key again and enter only the raw value. |
| No clients appear | The API key cannot access any Infima clients. | Confirm that the key has access to at least one client. |
| Clients appear but contacts are missing | User access or a client-user request failed. | Confirm user access in Infima and retry the sync. |
| Some security-awareness data is missing | The data type is not included in the integration or is unavailable for that user or client. | Confirm that the data exists in Infima and review the supported objects described above. |
| The integration remains in a syncing state | The initial sync is still running or a vendor request failed. | Wait for the sync to finish, then review the integration status and retry. |
| The vendor returns a rate-limit response | Too many requests were made in a short period. | Wait and retry the sync. |
Related resources
| Any questions? Reach out to our Lifecycle Manager support team by submitting a support ticket. |
|
|