New hire spend onboarding from Ashby to Ramp

Build me an agent workflow that provisions Ramp spend access for every new hire the moment they are marked Hired in Ashby, then announces them in Slack.

Trigger: poll Ashby for the candidate_hired event. Each fire gives me an application that just transitioned to Hired.

For each hired candidate, the agent should:

1. Call Ashby "Get Candidate Info" using the candidate id from the trigger payload to pull the candidate's full name, primary email, the role they were hired into, and their team or department.

2. Call Ramp "Invite User" to invite that person to Ramp using their email and assign them to the department that matches their team. Wait on the returned task id until the user is created, since this operation is async-deferred.

3. Decide a sensible monthly spend limit and category restrictions based on role and department. This is the agent's judgement call. As a starting heuristic: sales and customer-facing roles get a higher travel and entertainment limit (think client dinners, flights), engineering and product roles get a software and SaaS-focused limit, marketing gets an ads and events limit, and everyone else gets a modest general-purpose limit. Keep amounts conservative defaults and let the operator tune them later.

4. Call Ramp "Create Limit" with that amount, the right category restrictions, and the new user as the limit's owner. Wait on the returned task id until the limit is created.

5. Call Ramp "Create Virtual Card" tied to the spend limit you just created and assigned to the new user, with a display name like "<First Name> <Last Name> onboarding card". Wait on the returned task id until the card is fully provisioned.

6. Call Slack "Send a Message" to post a welcome message in our onboarding channel (the operator should set the channel id at install time). The message should introduce the new hire by name and role, mention the team they are joining, and confirm that their Ramp account is set up with a virtual card and a role-appropriate spend limit. Keep the tone warm and brief, two or three sentences.

Important details: all three Ramp operations (Invite User, Create Limit, Create Virtual Card) return task ids and complete asynchronously. Poll each task to completion before moving to the next step so we never reference a user, limit, or card that is not yet provisioned. If any step fails, post a short error message in the same Slack channel tagging the operator instead of silently dropping the hire.

The role-to-limit mapping should be expressed in the agent's instructions so an operator can edit it in plain English without touching code.