MILabs
Integrations

Lead routing automation for JobAdder

Route inbound enquiries to the right JobAdder consultant with rules your agency sets, a named owner and a log of each decision.

Updated 2026-08-20

Lead routing automation with JobAdder

Recruitment agencies on JobAdder often get enquiries from several directions at once: referral emails, website forms and calls noted by reception. This build reads each new enquiry as it arrives, compares it with the rules your agency sets, and passes it to the consultant who covers that sector or client. The routing layer decides where a lead goes. JobAdder stays the system where the work is recorded. For a small agency the practical gain is that a referral does not sit unread while the sector lead is away. Because the build depends on the account's API access, the first conversation is about which records your credentials can read and write. Consultants still make the calls and manage placements. The routing step only answers who should pick up an enquiry first, and it logs that answer so a manager can review it later.

How it works

  1. Confirm which JobAdder records your API credentials can read and which fields can be written back, and record that list before any rule is built.

  2. Connect the enquiry sources, such as the web form and the shared referral inbox, to a single queue that the routing layer reads.

  3. Write the matching rules in plain terms: sector, client account, region and the consultant who owns each.

  4. Where the account allows it, record the assigned consultant against the matching client or candidate record in JobAdder, and send anything that matches no rule to a fallback owner.

  5. Keep a log of each decision so a manager can see which rule fired and change it when the team changes.

good questions, straight answers

Frequently asked questions

Can a lead routing automation work with JobAdder data exports?
It can work with exports where they are available, but an export is a snapshot rather than a live link. A routing build needs to see a new enquiry and the current owner of a client as they change, so a file exported at intervals will lag behind. Exports suit reviewing past routing decisions or checking which sectors generate most enquiries. For live routing, the API connection is the more suitable route, subject to what your account's permissions allow.
What should I back up in JobAdder first?
Before any automation touches the account, export or otherwise copy the records the routing rules will read, including the client list, consultant assignments and any lead-source fields your team uses. Note which fields are custom to your agency, because those are often the ones a rule depends on and the ones most likely to break if renamed. Keep a copy of the current assignment list too, so you can compare behaviour before and after the build goes live.
How does a lead routing automation connect to JobAdder?
The usual route is the JobAdder API, which the vendor publishes for reading and updating some records. A routing layer built in a tool such as Zapier or Make, or in a custom service, sends requests through that API using credentials issued for your account. The enquiry sources connect separately, to the shared inbox or web form, and the routing layer reads from them.
Do I need a developer to connect a lead routing automation to JobAdder?
Not always. Simple rules that move enquiries between a form, an inbox and a single owner field can often be built in a no-code automation tool once API access is confirmed. A developer becomes useful when the rules depend on several records, need a fallback that reads live workload, or must write back to fields that are only reachable through custom work. Whoever builds it should document each rule and keep the credentials under the agency's control.
How does a lead routing automation stay in step with JobAdder?
Routing rules describe how the agency works, so they need regular review as sectors, client accounts and staff change. Each routed enquiry should carry a log entry showing the rule it matched and the owner it went to. A manager can then compare that log with JobAdder's own records and spot mismatches, such as a client reassigned without the routing rule being updated.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.