Skip to main content

Gumloop Agent Session

This integration holds a conversation with a Gumloop agent through the session API. It opens one session on the first turn, appends every later turn to that session, and returns the agent's reply. Gumloop keeps the conversation history, so the adapter carries only the session ID.

Required secrets​

SecretWhat it is
GUMLOOP_API_KEYPersonal API key, sent as a bearer token.
GUMLOOP_USER_IDGumloop user ID, sent in x-auth-key.
GUMLOOP_AGENT_IDID of the agent to converse with.

Personal API keys require the Pro plan or above.

Create the agent in Gumloop​

  1. In Gumloop, open Agents and create an agent.
  2. Choose its model and write its instructions.
  3. Save it, then send it a message in the Gumloop UI to confirm it answers.

Get the Gumloop values​

  1. Open Settings, then Connectors, and open the Gumloop API Key credential to read your personal API key.
  2. Open Settings, then Profile, and copy the user ID shown under your email address.
  3. Open the agent and copy its ID from the URL.

Set it up in Spec27​

  1. Open your project and select Agents.
  2. Choose Gumloop Agent Session from the registry.
  3. Enter the three secrets above.
  4. Send a test message and confirm the agent replies.

Turn support​

This integration supports single-turn and multi-turn evaluations. The adapter creates the session on the first turn and appends later turns to it, so the agent keeps its context.

Limitations and notes​

  • The adapter returns the text parts of each new assistant message. It does not serialize tool calls, citations, or attachments.
  • It waits for the session to reach idle or completed before reading the reply, and fails the turn when the session reports failed.
  • A session that produces no assistant message within the polling budget fails the turn rather than returning empty text.
  • Evaluations create real sessions and consume Gumloop credits.