Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Letta

Letta is the platform for building stateful agents: open AI with advanced memory that can learn and self-improve over time.

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Letta with Flows360

Letta is the platform for building stateful agents: open AI with advanced memory that can learn and self-improve over time.

Use the Letta connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 2 triggers.

Available actions

  • Create Agent From Template
  • Create Identity
  • Send Message to Agent
  • Get Identities

Available triggers

  • New Agent
  • New Message

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Letta
  • Package: @activepieces/piece-letta@0.1.7
  • Exact artifact digest: sha256:a9e59db1b4734073a03530e20f6532384c46f8c973feedf7b3e90740bd1ed00a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Agent From Template (createAgentFromTemplate), Creates an agent from a template Classification: read.
  • Create Identity (createIdentity), Creates a Letta identity Classification: read.
  • Send Message to Agent (sendMessageToAgent), Send message to an agent Classification: read.
  • Get Identities (getIdentities), Searches for identities in your Letta Project Classification: read.

Trigger contracts

  • New Agent, polling.
  • New Message, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions4
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Optional · protected credential
  • Base URL Optional

Supported objects

ObjectReadWriteNotes
Create Agent From Template Yes No Creates an agent from a template
Create Identity Yes No Creates a Letta identity
Send Message to Agent Yes No Send message to an agent
Get Identities Yes No Searches for identities in your Letta Project
New Agent Yes No polling trigger declared by the pinned package.
New Message Yes No polling trigger declared by the pinned package.

Supported actions

Create Agent From Template · Read

Creates an agent from a template

create_agent_from_template · Risk: low · Retry: safe

Inputs

  • templateVersion · string · Required, The template version ID to create the agent from
  • agentName · string · Optional, The name of the agent (optional, a random name will be assigned if not provided)
  • identityIds · array · Optional, Select identities to assign to the agent
  • tags · array · Optional, Tags to assign to the agent
  • memoryVariables · object · Optional, Memory variables to assign to the agent (key-value pairs)
  • toolVariables · object · Optional, Tool variables to assign to the agent (key-value pairs)
  • initialMessageSequence · array · Optional, Initial sequence of messages to start the agent with
Create Identity · Read

Creates a Letta identity

create_identity · Risk: low · Retry: safe

Inputs

  • identifierKey · string · Required, External, user-generated identifier key of the identity
  • name · string · Required, The name of the identity
  • identityType · string · Required, The type of the identity
  • projectId · string · Optional, The project ID of the identity (optional)
  • properties · array · Optional, List of properties associated with the identity
Send Message to Agent · Read

Send message to an agent

send_message_to_agent · Risk: low · Retry: safe

Inputs

  • agentId · string · Required, Select the agent to send a message to
  • input · string · Required, The message content to send to the agent
  • maxSteps · number · Optional, Maximum number of steps the agent should take to process the request
Get Identities · Read

Searches for identities in your Letta Project

get_identities · Risk: low · Retry: safe

Inputs

  • identifierKey · string · Optional, Filter by identifier key
  • name · string · Optional, Filter by identity name
  • identityType · string · Optional, Filter by identity type
  • projectId · string · Optional, Filter by project ID
  • limit · number · Optional, Maximum number of identities to return

Triggers

New Agent · Poll

Triggers when a new agent is created

New Message · Poll

Triggers when an agent uses send_message

Inputs

  • agentId · string

Setup

Setup

  1. Add the Letta connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API Key (apiKey), optional; stored as a sensitive connection value.
  • Base URL (baseUrl), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-letta@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Letta connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-letta@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com