New hire ops onboarding from Ashby to Linear and Notion

Build an agent workflow that runs whenever a candidate is marked Hired in Ashby. Use Ashby's poll trigger with the candidate_hired event type so the workflow fires once per newly hired candidate.

When the trigger fires, gather context from Ashby:

1. Call Ashby Get Candidate Info to load the candidate's name, primary email, location, and any tags.

2. Call Ashby Get Application Info for the application that triggered this event to find the linked job, the recruiter, and the hiring manager.

3. Call Ashby Get Job Info on that job to read the job title, department, location, and employment type.

4. Call Ashby Get Offer Info on the application's accepted offer to read the start date, level/seniority, and any compensation context relevant to the welcome doc (do not include compensation in any IT-visible content).

Before doing any work, call Linear Search Issues with a query that includes the candidate's full name and the phrase 'IT provisioning' (and the candidate's Ashby ID if available). If a matching open or recently created issue already exists for this candidate, stop and do nothing. This prevents duplicates on re-runs.

If no existing ticket is found, in parallel do the following two actions:

A) Use Linear Create Issue against our IT team to file a provisioning ticket. The title should be 'IT provisioning: <Full Name> (<Job Title>) — starts <Start Date>'. The description should include: candidate name, role, department, manager, start date, work location, and a checklist of provisioning items: laptop type (default to MacBook Pro 14" unless the role suggests otherwise), the baseline software access list (Google Workspace, Slack, 1Password, Zoom, our HRIS), plus role-specific tools the agent infers from the job and department. Use these defaults that I can edit later: Engineering → GitHub, AWS, Linear, Sentry, Vercel. Sales → Salesforce, Gong, Outreach, LinkedIn Sales Navigator. Marketing → HubSpot, Figma, Canva. Design → Figma, Loom. Finance/Ops → Ramp, NetSuite. Set priority based on time to start date: under 7 days = Urgent, 7–21 days = High, 22–45 days = Normal, more than 45 days = Low. Include the Ashby candidate URL in the description for traceability.

B) Use Notion Create a Page in our onboarding database to draft a personalized welcome page for the new hire. The page title should be 'Welcome, <First Name>! — <Job Title>'. Populate the page with sections: a warm intro paragraph addressed to the hire; key details (role, team, manager, start date, location); a first-week schedule placeholder (Day 1 orientation, Day 2 team intros, Day 3 tooling setup, Day 4 shadow a teammate, Day 5 retro with manager); a 'Meet your manager' section with the manager's name and a placeholder for a short bio; a 'What this role does' paragraph synthesized from the job description; and a 'Helpful links' section with placeholders for our handbook, org chart, and team page. Set any database properties that are required (e.g. Status = Draft, Hire Type = New Hire, Start Date).

After both actions complete, the workflow is done. Do not send any email; a separate workflow handles the candidate-facing welcome email. Log the Linear issue URL and Notion page URL so they can be reviewed.

Failure handling: if Ashby returns missing fields (e.g. no manager assigned), still create both artifacts but flag the missing fields clearly in the Linear description and at the top of the Notion page so a human can fill them in.