[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Log call notes on JobDiva candidate records

> Turn your day of screening calls into JobDiva candidate notes with the right action type, and skip candidates already noted today.

Source: https://cotlet.dev/integrations/jobdiva-api-mcp-server/log-call-notes

After a day of screening calls, the notes sit in a notebook or a doc, and each one still has to be typed into the right candidate record.

Cotlet does it in your own JobDiva account with find\_candidate, list\_candidate\_notes and add\_candidate\_note, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=jobdiva) [All JobDiva tools](https://cotlet.dev/integrations/jobdiva-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can JobDiva do this on its own?

JobDiva's API can create, pin and delete candidate notes and can list note templates (checked 23 Oct 2026), but it needs a client ID from JobDiva. The app has no way to turn a text of call notes into notes on many records, and JobDiva has no MCP server.

## How you do it in JobDiva today

1. The recruiter finds the candidate by name, email or phone and opens the record.
2. The recruiter adds a note, picks an action type and a date, and links the note to an open job or a contact when the call was about one.
3. The note appears in the record's notes, where colleagues read the history before they call the same person.
4. This repeats for every candidate on a busy day, so notes are the first thing to slip, and a missing note means the next recruiter calls cold.

## How to log call notes on JobDiva candidate records

Prompt

```
Here are my call notes from today. For each candidate, find the record in JobDiva and add a note with the summary. Skip anyone who already has a note from today.
```

1. 01  
### Match each name to one record  
find\_candidate looks up the name, email or phone from your notes. When two records match, for example the same name in two cities, the agent compares location and occupation with your notes and asks you instead of guessing.
2. 02  
### Check what is already there  
list\_candidate\_notes reads the notes on the record. If a note from today already carries the same call, the agent skips the candidate, so running the job twice never doubles a note.
3. 03  
### Pick the action type  
The agent copies the action type from the candidate's earlier notes for the same kind of call. Action types are set up in your account, so when none fits, the agent asks which one to use.
4. 04  
### Link the job when you named one  
add\_candidate\_note saves the summary as the note text and passes the job id when your notes name an open job. A note about a client contact is left unlinked, because the tool takes no contact link.
5. 05  
### Report what it saved  
The agent lists every candidate noted and every one it skipped, with the reason, so you can open any record and see the note.

### What you get back

Example data

```
Calls in your notes: 6
Notes added 4 (Phone Call):
- Priya Raman: "Open to contract at 90 USD/h, free from 3 Nov"
- Marcus Lee: "Wants permanent, not relocating"
Skipped 1 (a note from today already exists)
Needs you 1: two records named Sam Ortiz
```

### Other ways to ask

- Log my call notes, link each note to job 24071835 and show me the list before you save anything.
- Every evening, read my notes doc and add a note for each candidate I named.
- Add a note to every candidate on this list saying the client closed the job.

## What JobDiva allows, and what to know first

- A JobDiva candidate note carries an action type and an action date, and can be linked to an open job or to a contact.
- JobDiva keeps note templates for candidates, so a team can have standard wording for a call type.
- JobDiva lets a user pin a candidate note, which keeps it on top of the notes list.
- JobDiva's quick candidate search matches first name, last name, email, alternate email, work, home and cell phone, fax and address.

add\_candidate\_note changes only your own JobDiva data and reach no one else, so it runs without asking first.

Sources: [JobDiva API (Swagger UI, Version 2)](https://api.jobdiva.com/jobdiva-api.html) · [JobDiva: Integrate with JobDiva](https://www.jobdiva.com/integrate)

## Call add\_candidate\_note from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/jobdiva/candidates/5821904/note \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"note":"Open to contract at 90 USD/h, free from 3 Nov. Not relocating.","action":"Phone Call","job_id":24071835}'
```

Example response

```
{
"note_id": 90214531,
"candidate_id": 5821904,
"action": "Phone Call",
"job_id": 24071835,
"status": "saved"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jobdiva\_write → add\_candidate\_note. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/jobdiva-api-mcp-server.md#automations)

## JobDiva tools this automation uses

__Cotlet JobDiva tools used to log call notes on JobDiva candidate records__
| Tool | Parameters |
| ---------------------- | ------------------------------------ |
| find\_candidate | value, limit |
| list\_candidate\_notes | candidate\_id |
| add\_candidate\_note | candidate\_id, note, action, job\_id |

[All 14 JobDiva tools with descriptions](https://cotlet.dev/integrations/jobdiva-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect JobDiva to Cotlet?

Yes. You sign in to JobDiva yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JobDiva once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More JobDiva automations

- [Build a JobDiva candidate hotlist for a new job](https://cotlet.dev/integrations/jobdiva-api-mcp-server/build-candidate-hotlist.md)
- [Submit shortlisted candidates to a JobDiva job](https://cotlet.dev/integrations/jobdiva-api-mcp-server/submit-candidates-to-a-job.md)
- [JobDiva API and MCP server: every tool](https://cotlet.dev/integrations/jobdiva-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to JobDiva.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with JobDiva.

[Sign up free](https://cotlet.dev/app/signup?app=jobdiva)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.