Skip to main content
Book a demo

Connect Adobe Marketo Engage to Codex

Give Codex governed access to Adobe Marketo Engage’s 118 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Adobe Marketo Engage to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Add Adobe Marketo Engage to Runlayer

    Adobe Marketo Engage isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Adobe Marketo Engage’s 118 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Adobe Marketo Engage

    Sign in the way Adobe Marketo Engage requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Adobe Marketo Engage from Codex

    Adobe Marketo Engage’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

118 Adobe Marketo Engage tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Activate smart campaign

    Activate a smart campaign to start processing leads.

  • Add field set

    Add a field set (field group) to a form.

  • Add field to form

    Add a new field to a form.

  • Add field visibility rule

    Add visibility rules to a form field.

  • Add flow step

    Add a flow step to a smart campaign at the specified index.

  • Add flow step choice

    Add a conditional choice branch to an existing flow step, so the step can do different things for different leads ("if the lead is in California send email A, otherwise send email B").

  • Add leads to list

    Add existing leads to a static list (list membership).

  • Add rich text field

    Add a rich text element to a form.

See all 118 Adobe Marketo Engage tools

Control

What Runlayer can see and stop in Codex

Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.

  • Gateway policy (available)

    Every Adobe Marketo Engage call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination