Upcoming events / Webinar

Tray Headless: Shifting your integration architecture to headless

A working session on the shift from low-code to headless enterprise integration. What it means, how to balance it with low-code, and a live build inside Claude Code using Tray as MCP services.

Webinar ·10:00 AM PDT / 1:00 PM EDT

Paul Turner

Paul Turner

VP of Market Strategy

Niels Fogt

Niels Fogt

Sr. Director, Automation Solutions

The integration layer is the last part of your stack that hasn’t been opened up, and it’s holding teams back. Developers are shipping inside Claude Code, Cursor, and the AI IDE they already use every day. The integration platform that doesn’t meet them there gets left behind in the browser.

Join Paul Turner and Niels Fogt for a working session on the shift from low-code to headless enterprise integration. They’ll walk through what “headless” actually means for IT and integration teams, how to balance with low-code, and what to look for from capabilities to governance.

The session ends with a live build. Niels constructs an integration end-to-end inside Claude Code, using the full Tray platform running as MCP services.

You’ll leave this session knowing

  • Why a headless approach matters, and what it changes for your team
  • What to look for in a genuinely headless iPaaS, and the questions to ask vendors
  • How Tray Headless works in practice, from prompt to production

You’ll walk away with a clear point of view on where integration is going, and a concrete sense of what your team should be asking for next.

Why this matters

The shift is already happening, and most integration teams haven’t named it yet.

A senior engineer joins. They open Claude Code on day one, because that’s where they already write everything else. They look for the integration platform inside their IDE. It isn’t there. So they write a script. Or they file a ticket and wait. Or they build it directly in the canvas, which works, but they don’t reach for it again.

Multiply that across a year of hiring, and the platform you bought to be the integration backbone is being used by half the people who should be using it. The other half are working around it, in tools you don’t see.

The platform isn’t the problem. The surface is. And the gap between where developers work and where the iPaaS lives is what headless integration is built to close.

What you’ll walk away with

  • A real definition of headless integration. Not the marketing version. What it means for build, governance, and how your team operates day to day. Specific enough that you can take the framing back to your own architecture review.
  • The questions to ask iPaaS vendors before you commit. A short list of the capabilities that separate a genuinely headless platform from one that bolted MCP onto the side. If you’re evaluating tools for H2, these are the questions that surface the difference.
  • A live build of a Customer 360 integration end-to-end inside Claude Code. Niels Fogt, who leads this work at Tray, takes the integration from prompt to production. Config files, connector discovery subagent, validation hooks, the CDK extension. 23 MCP tools across the full workflow lifecycle. Pre-flight error prevention and quality hooks running in the background.
  • The cross-IDE walk. Same Tray platform running as MCP services in Cursor and Codex. Five minutes, side by side. Shows what platform-neutral actually looks like in practice.
  • How governance holds when builds come from any IDE. Audit, policy, access control. The piece IT can’t compromise on, and the part most “AI IDE” pitches skip over. We’ll show how the governance layer stays as the platform, not the IDE.

This session is for you if:

  • Your developers are already working in Claude Code, Cursor, or Codex, and your integration platform isn’t there
  • You’re being asked to support AI development and aren’t sure what that should look like for your iPaaS
  • Your team is running on Workato, MuleSoft, or Boomi and you’re sizing up what comes next
  • You’re an IT leader who needs the governance story to hold up before you green-light builds from the IDE
  • You’re already on Tray and want to see how Tray Headless fits alongside Tray Build

Agenda

45 minutes, structured to respect your calendar:

  • The shift, framed (10 minutes)
  • Live build of a Customer 360 integration inside Claude Code (25 minutes)
  • The same platform running in Cursor and Codex (5 minutes)
  • Live Q&A (5 minutes)

Common questions

What if I can’t make it live? Register anyway. We’ll send the recording within 24 hours. The live build and the Q&A are the parts most worth your time.

Is this a sales pitch? The first 10 minutes are framing, the next 25 are a real build. We’ll show Tray Headless because it’s the platform we built for this. The questions to ask vendors and the architecture frame work whether you ever buy from us or not.

Can I share this with my team? Please do. Forward the registration link, or send them the replay after.

We’re already running on Tray. Does this change anything for us? Tray Headless sits alongside Tray Build on the same platform. Nothing breaks. The session is worth your time if you have developers who’d rather build from their IDE, or if you’re sizing up a self-service motion across the org.

What if my team uses Cursor or Codex, not Claude Code? Tray Headless MCP runs the full platform as MCP services in any MCP-compatible IDE. The cross-IDE walk at minute 35 shows it. Platform-neutral, no lock-in.