jobhunt.app/mcp

Keep people and context together

Recall saved conversations and record only what you know.

Updated

Step by step

  1. Find the right person

    Search your saved contacts and companies. If names are ambiguous, choose the right record before opening its history or making a change.

  2. Read saved conversation history

    Open the person’s record and follow any additional history pages. Keep the saved dates and record identities; an incomplete page is not a complete history.

  3. Record what happened

    When you ask to save a conversation, JobHunt records only the facts you provide on the selected contact. Keep when the conversation happened separate from when you recorded it. If you do not know when it happened, the agent asks or saves it as an explicitly undated note, because a recorded interaction always carries a date. Recording a conversation does not send a message.

What happens next

Your saved history stays connected to the selected person and job-search work.

Troubleshooting

Saving a contact does not email them or find private contact details. Check for an existing contact before adding a duplicate.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist workspace crm

Read one owned CRM page. Counts and filters apply to this page; follow has_more.

GET /api/v1/journey/list_workspace_crm_v2

DECLARED PERMISSIONS

  • read:contacts
  • read:companies
  • read:applications
View input, output and access requirements →
READget workspace crm

Read an owned contact or company with a page of related notes, tasks, applications and history. Follow related_has_more by increasing related_page; never infer missing records from one page.

GET /api/v1/journey/get_workspace_crm_v2

DECLARED PERMISSIONS

  • read:contacts
  • read:companies
  • read:applications
  • read:tasks
View input, output and access requirements →
WRITEsave workspace contact

Save an explicitly reviewed owned contact action. Existing records require the exact fingerprint. Deletion unlinks relationships but preserves applications. Interaction notes record a conversation; they never send a message. Reuse the same request ID after an uncertain response.

POST /api/v1/journey/save_workspace_contact_v2

DECLARED PERMISSIONS

  • write:contacts
View input, output and access requirements →