jobhunt.app/mcp

Draft outreach with your agent

Prepare a message from saved relationship context.

Updated

Step by step

  1. Choose the saved contact

    Ask your connected agent to draft a message to someone you know. It checks for the right saved person and clarifies if names are ambiguous.

  2. Use the right context

    The agent reads relevant notes and recorded interactions, then drafts only from facts you supplied or confirmed. It leaves unknown details out and does not include unrelated application or resume information.

  3. Review the complete draft

    Check the recipient, channel and full message in chat. Edit the words until they sound right to you. Producing a draft alone does not change your saved records.

  4. Save only the approved wording

    If you ask to save it, keep the approved version as a clearly labeled “Draft — not sent” note on the selected person or company. A later revision updates that same note. Saving a draft does not add a sent interaction, change last-contacted history or complete a task.

  5. Send it yourself

    The message is a draft for your review. JobHunt does not send, schedule or record it as sent.

What happens next

You have message text to review and send through your own channel when ready.

Troubleshooting

If the agent cannot read the relationship history or resolve the intended person, it should say what is missing rather than invent context or recipient details.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READsearch workspace

Search the same saved applications, contacts, companies, resumes, tasks and Hunts as browser workspace search. Returns up to ten ranked owned matches, not a full inventory.

GET /api/v1/journey/search_workspace_v2

DECLARED PERMISSIONS

  • read:applications
  • read:contacts
  • read:companies
  • read:documents
  • read:tasks
  • read:campaigns
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 →
READlist workspace activity

Read a page of the same owned work-history timeline as the browser. Follow has_more. The browser timeline combines application history with the latest 500 account events; it is not a complete audit export.

GET /api/v1/journey/list_workspace_activity_v2

DECLARED PERMISSIONS

  • read:activity
  • read:applications
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 →
WRITEsave workspace company

Save an explicitly reviewed owned company 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_company_v2

DECLARED PERMISSIONS

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