Integrations in Wamly bring your third-party hiring tools, custom API connections and event notifications together in one place, so you can manage the entire candidate journey — from attraction to background verification — without juggling separate exports. They all live under the Integrations tab in My Organisation, which houses three sections: Integrations, Service Accounts and Webhooks.

Access to the Integrations tab is available to users with the relevant permissions (for example the IT role, which grants access to the Developer Portal — integrations, API keys and webhooks). Other users may see it but find it locked.

Accessing the Integrations Tab

• Navigate to the left-hand menu.
• Click My Organisation to open the settings view.
• Open the Integrations tab. You'll see three sections: Integrations, Service Accounts and Webhooks.

Integrations

Connect supported third-party applications through our built-in integrations (such as Adzuna).

• Click Add integration.
• Choose your integration from the list, enter the API Key, and complete the configuration.
• Click Connect — a Success message confirms the integration (for example your ATS) is connected.
• Each integration's status (for example Configured) is shown in the list; use the three-dot menu to manage it.

For a detailed guide on integrating with Adzuna, see this article.

Service Accounts

Create service accounts to build custom integrations using our API. A service account is a non-human identity for integrations and API clients that need to talk to Wamly on behalf of your organisation. Each has a name, its own permissions (assigned via roles), and one or more API tokens — but it can't log in and doesn't take up a seat.

• Click Create to add a service account, give it a descriptive name, and assign a role.
• Manage its API tokens (create, label and revoke) from the service account. Token values are shown only once at creation, so copy and store them safely.

For the full detail on service accounts and API tokens, see the User Permissions Guide.

Webhooks

Create webhooks to send data and events to external services. Webhooks push information to an external system the instant a chosen event is triggered — no polling required. You can add multiple webhooks per event to send candidate data to several systems at once (a CRM, a database, an ATS, or an internal Slack alert).

To create a webhook:

• In the Integrations tab, go to the Webhooks section and click + Create.
• Enter a name, the Webhook URL to call, and select the event type that should trigger it:
  • Project Creation — a new project is created.
  • A New Interview — a candidate completes an interview.
  • A New Rating — a new rating is given to a candidate.
  • A Project Edit — the project has been edited.
  • A candidate's interview status changes.
  • A Psychometric Assessment status is updated.
  • A Background Check status is updated.
  • A candidate is assigned to a rater.
  • A candidate's tag(s) change.
• Click Create. Webhooks can be edited, deactivated or deleted from this section.

Webhook use case example

When a candidate is moved to the “Hired” stage, push their info into an employee management system like SAP SuccessFactors or Zoho People.

Example using Make.com and Zoho People:

• Step 1: Create a new scenario in Make and use the incoming webhooks module. Copy the URL it provides.
• Step 2: In Wamly, navigate to My Organisation >> Integrations >> Webhooks and create a new webhook.
• Step 3: Give the webhook a name, paste the URL from Step 1 into the Webhook URL field, and choose the “Candidate interview status change” event.
• Step 4: Back in your Make scenario, add the Zoho People “add record” module with a filter that only allows records where the stage is “Hired”.
• Step 5: Map the candidate information from the webhook into the Zoho People “add record” module.
• Step 6: When a candidate's stage changes to Hired, the webhook triggers and your Make automation runs, so the candidate's information appears in Zoho People.