Migrate Slack-Triggered Browser Automation from Browser-Use to n8n + Skyvern

Project overview I run a tutoring business. We have a working automation that monitors a Slack channel for tutor-match requests, extracts calendar availability data from TutorBird (behind a login), cross-references a Google Sheet roster with a lot of data for each tutor, and posts a ranked list of matching tutors back to Slack as a threaded reply. The system currently runs on Browser-Use's cloud platform and is unreliable — it's expensive and often breaks, and I want to move to a more predictable stack. I have complete, detailed spec files for the existing workflow that will inform the rebuild. What you'll be building A production-grade workflow orchestrated in n8n (I'll pay for n8n Cloud) that: Triggers in real time via Slack's Events API (no cron polling) — the workflow starts within seconds of a new message in the target channel Filters eligible messages as the first step (regex + reaction-based dedupe); ineligible messages exit immediately For each eligible request: Reads a tutor roster from a Google Sheet Triggers a Skyvern workflow to log into TutorBird and extract tutor availability windows for the relevant days Calls the Anthropic API (Claude Sonnet 5) with a matching prompt to rank tutors against the client's requirements Posts the ranked result as a threaded Slack reply Manages reaction state on the original message (🔄 while processing → ✅ on success, ❌ on failure) Handles error cases and dedupes cleanly Includes a lightweight hourly safety-net workflow that scans for messages with a processing reaction but no completion reaction, and re-runs any it finds (belt-and-suspenders for the rare case of a missed Slack webhook) Deliverables The main event-driven n8n workflow implementing the above The hourly safety-net n8n workflow for missed-webhook recovery One Skyvern workflow for the TutorBird availability extraction, with Route Memorization enabled and tested for stability Slack app configured with Events API subscriptions and correct OAuth scopes Documentation of secrets/credential setup (Slack app, TutorBird login, Google Sheet, Anthropic API key, Skyvern API key) A short runbook explaining how to monitor the workflow, common failure modes, and how to re-run a failed request Handoff call (30–60 min) walking through the workflow, testing a live request end-to-end What I'll provide Full spec files from the current Browser-Use system (well-documented, ~4 markdown files) — these describe the exact business logic, edge cases, and matching rules. Much of this ports over; some (the cron/state-machine parts) becomes unnecessary in an event-driven architecture, which should reduce implementation time. TutorBird login credentials Google Sheet with the tutor roster Slack workspace admin access (I'll create the Slack app; you'll advise on required scopes) Anthropic API key n8n Cloud and Skyvern accounts (I'll set up billing; you'll build inside them) The current Claude prompt used for matching logic (can be reused mostly as-is) Stack Orchestrator: n8n Cloud Trigger: Slack Events API (via n8n's native Slack Trigger node) Browser automation: Skyvern (Pro plan — for Route Memorization, credential storage, and 2FA support) LLM: Anthropic API, Claude Sonnet 4.6, with prompt caching properly configured Data source: Google Sheets (via native n8n node) Messaging: Slack (via native n8n node) Target site: tutorbird.com (browser automation only — no public API for what we need) Scope boundaries In scope: Everything listed under "What you'll be building" above Reasonable retry/error handling Basic observability (n8n's built-in execution logs are sufficient; no custom dashboards needed) Out of scope (for this engagement): Ongoing maintenance beyond a 2-week bug-fix window post-delivery New feature development beyond the current spec Migrating historical data — the new system starts fresh Custom UI or dashboards Ideal candidate Real n8n experience (please share a link to something you've built or a workflow screenshot) Comfort with Slack Events API (webhook subscriptions, URL verification, OAuth scopes) — not just posting to Slack channels Comfort with browser automation platforms — Skyvern experience preferred but not required if you've done similar work with Playwright, Browserbase, or browser-use Understanding of Anthropic API prompt caching (this matters for cost) Comfortable reading detailed spec docs and asking clarifying questions before building Budget and timeline Please quote your fixed price with rationale, plus your estimated hours. I have detailed specs already written, which should reduce discovery time meaningfully — I'm looking for candidates who read the specs before quoting, not developers who assume everything from scratch. Timeline: I'd like this working in production within 2–3 weeks of kickoff. To apply Please include: A brief note (not a form letter) on what part of this project feels straightforward for you and what feels harder One example of a similar workflow automation you've built (link or screenshot) Your fixed-price quote and estimated hours to complete Any clarifying questions I'll respond within 48 hours to promising candidates.