Integrations & Onboarding Engineer

BuzzTrail is an AI sales companion — realistic video avatars conduct live product demos with real-time voice conversations. Think of it as an AI sales rep that greets prospects on your website, qualifies them, answers product questions, and books a follow‑up meeting — all without a human in the loop. We are in production with paying customers and growing fast. You are the person who makes BuzzTrail work inside a customer’s world. That means two things: you talk to customers to understand what they need, and you build the integrations that deliver it.

Half your week is on calls figuring out what a customer’s CRM setup looks like and what data they want flowing where. The other half is wiring it up — N8N workflows, webhook payloads, API connections, and onboarding automation. This is not a pure engineering role and it’s not a pure customer role. It’s both. You’re technical enough to build real integrations and articulate enough to run a discovery call with a VP of Sales who just wants their HubSpot updated after every AI meeting.

• Customer Integration Discovery (High Priority)
  • You’re the first person customers talk to about integrations. What CRM do they use? What fields matter? What happens after a meeting ends — does the lead need to land in a specific pipeline stage? Do they want transcripts in Salesforce? Follow‑up emails triggered from HubSpot workflows?
  • Discovery calls — understand each customer’s CRM, marketing automation, and sales workflow stack
  • Integration mapping — document what data flows where, which fields map to what, and what triggers what
  • Requirements gathering — turn customer conversations into actionable specs the engineering team can build against
  • Pattern recognition — identify common integration patterns across customers to prioritise platform features over one‑off builds
  • Feedback loop — bring customer needs back to product. You’ll shape the integration roadmap because you’re closest to what customers actually ask for
• N8N Workflow Automation (High Priority)
  • N8N is our integration hub. We’re self‑hosting it and using it to connect BuzzTrail to everything our customers already use — CRMs, marketing automation, calendars, Slack, email platforms, and whatever else comes up. Instead of building custom integrations for every platform, you build N8N workflows.
  • Workflow design — build N8N workflows that receive BuzzTrail webhook payloads and route data to HubSpot, Salesforce, Pipedrive, and others
  • Multi‑tenant architecture — one N8N instance serving multiple customers, each with their own credentials and field mappings
  • CRM connectors — HubSpot, Salesforce, Pipedrive, Zoho, Close — build and maintain connectors for the CRMs our customers use
  • Post‑meeting data routing — meeting outcomes, summaries, action items, transcript links — all flowing to the right CRM fields
  • Pre‑meeting lead creation — intake form submissions creating or updating CRM contacts before the meeting starts
  • Beyond CRM — our customers use a wide range of tools and BuzzTrail meeting data needs to flow into all of them.
• Customer Onboarding
  • You own the technical side of getting new customers live. Not the sales process — the part after they sign up where everything needs to actually work.
  • Account setup — configure their workspace, avatar, domains, and knowledge sources
  • CRM integration setup — connect their CRM via N8N, map fields, test webhook delivery, verify data lands correctly
  • Embed integration — help customers add BuzzTrail widgets to their websites
  • Third‑party connections — wire up whatever else the customer uses: Slack, calendar tools, marketing automation, analytics platforms
  • Go‑live support — be available when they flip the switch, monitor the first few meetings, catch issues early
  • Onboarding playbook — build and refine a repeatable onboarding process that scales beyond you
• API Monitoring & Maintenance
  • You’re integrating with dozens of third‑party platforms. They all change — deprecations, new API versions, auth flow changes, rate limit adjustments, new fields, sunset notices. If you don’t stay on top of it, integrations break silently.
  • Changelog tracking — monitor API changelogs, developer blogs, and deprecation notices across every platform we integrate with
  • Version management — track which API versions our N8N workflows use, plan upgrades before old versions get sunset
  • Breaking change response — when a platform ships a breaking change, assess impact across all affected customer workflows and fix them before they break
  • Rate limit monitoring — track usage against each platform’s rate limits, adjust workflow timing and batching as customer volume grows
  • Auth changes — OAuth scope changes, token lifetime changes, new auth requirements — catch these before customers start seeing failures
  • New capabilities — when platforms ship new APIs or fields, evaluate whether they unlock better integrations for our customers
  • Integration health dashboard — build and maintain visibility into which integrations are healthy, which are degraded, and which need attention
  • Vendor communication — join developer programs, attend webinars, maintain relationships with partner/dev teams at key platforms
• External API & Webhooks
  • We’re building a public API and webhook system so customers can integrate programmatically. You’ll drive what gets built based on what customers actually need.
  • Webhook payloads — define what data gets sent when meetings start, end, transcripts are ready, recordings are available
  • API requirements — shape the public REST API based on real customer requests (meeting data, transcripts, recordings, knowledge source management)
  • Documentation — write API docs and integration guides that customers can actually follow
  • Developer experience — make the integration story smooth enough that a customer’s developer can self‑serve

You Have Customer Skills

• You’ve done discovery calls, onboarding calls, or technical implementation calls with customers — you’re comfortable on camera with non‑technical stakeholders
• You can translate "I want my Salesforce updated" into a technical spec
• You’ve worked in a customer‑facing technical role before: solutions engineer, forward‑deployed engineer, integrations engineer, technical CSM, or similar
• You have opinions about what makes a good onboarding experience

Integration & Automation

• CRM experience — you’ve integrated with at least two of: HubSpot, Salesforce, Pipedrive, Zoho, Close
• You’ve connected to tools beyond CRM — marketing automation, CDPs, scheduling platforms, enrichment APIs, or similar. You don’t need to know every tool in the table above, but the category names shouldn’t be foreign to you
• Webhook architecture — you understand payloads, retries, idempotency, HMAC signing
• OAuth flows — you’ve connected to third‑party APIs and managed token lifecycle

Technical Foundation

• N8N is the core skill — you’ve built and maintained production N8N workflows, not just prototyped with them
• You know N8N’s node ecosystem, credential management, error handling, and execution modes
• Comfortable self‑hosting N8N and managing upgrades, backups, and scaling
• JSON, HTTP, and webhooks are second nature — you can read a payload and know what to do with it
• You can debug a broken workflow by reading execution logs, inspecting payloads, and tracing data through nodes

Bonus

• Revenue operations or sales ops background (you speak the language of pipeline stages, lead scoring, ABM, and CRM hygiene)
• Built multi‑tenant SaaS integrations (credential isolation, per‑customer config)
• Experience with CDPs (mParticle, RudderStack, Segment) or reverse ETL tools
• Familiar with revenue intelligence platforms (Gong, Clari, 6sense)
• Experience with Supabase, PostgreSQL, or similar

What You’ll Ship First

• Your first 90 days, roughly in order:
• Shadow customer calls — understand our customers, their CRMs, and what they’re asking for
• First N8N workflows — HubSpot and Salesforce post‑meeting data routing for our existing customers
• Onboarding playbook v1 — documented, repeatable process for getting a new customer live
• Webhook payload spec — define what our post‑meeting webhooks should contain based on real customer needs
• First solo onboarding — take a new customer from signup to live meetings with CRM integration working