Scenarios

Overview

These sequences name the tools to call. Product rules and the clicks in the Leadline UI stay in Product Knowledge and Playbooks — follow those links instead of guessing fields.

Look up a position

Use this when you know a title, a numeric id, or whether the role is published or open.

1. searchPositionsTiny — title or id lookup. Pass published: 1 for live jobs and published: 0 for unpublished ones. Pass active: 1 for open hiring.
2. getPosition — load the position from the id the search returned.

What a Position is, and which fields matter, is in 111 - Positions.

Create an unpublished position

1. createPosition — creates an unpublished position. The title is required.
2. Finish workflow, application form, and pages before publishing. The human steps are in 401 - Create-Position.
3. publishPosition — only after those publish requirements are met.

createPosition and publishPosition change data immediately.

Answer a product question

Use this when the question is about how Leadline works, not about a live record.

1. searchProductKnowledge for what a feature is and the rules around it.
2. searchPlatformHowTo when the person wants the clicks in the portal.
3. getNote with the note id from the search when the full note is needed. A Product Knowledge id looks like 111 - Positions. A playbook id looks like 401 - Create-Position.

Do not use knowledge tools to list or update positions, candidates, or submissions.