Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

GoodMem

Store documents as memories with vector embeddings and perform similarity-based semantic retrieval using GoodMem

CategoryArtificial Intelligence
Authenticationcustom
Version0.0.5
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect GoodMem with Flows360

Store documents as memories with vector embeddings and perform similarity-based semantic retrieval using GoodMem

Use the GoodMem 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 5 actions and no declared triggers.

Available actions

  • Create Space
  • Create Memory
  • Retrieve Memories
  • Get Memory
  • Delete Memory

Available triggers

  • No triggers are declared in this pinned package.

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: GoodMem
  • Package: @activepieces/piece-goodmem@0.0.5
  • Exact artifact digest: sha256:083fa58ebb2ff326359e80510db96a45d637c43272c1fedd7f29c53e7381ab9e
  • 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 Space (create_space), Create a new space or reuse an existing one. A space is a logical container for organizing related memories, configured with embedders that convert text to vector embeddings Classification: read.
  • Create Memory (create_memory), Store a document as a new memory in a space. The memory is processed asynchronously - chunked into searchable pieces and embedded into vectors. Accepts a file or plain text. Classification: read.
  • Retrieve Memories (retrieve_memories), Perform similarity-based semantic retrieval across one or more spaces. Returns matching chunks ranked by relevance, with optional full memory definitions. Classification: read.
  • Get Memory (get_memory), Fetch a specific memory record by its ID, including metadata, processing status, and optionally the original content. Classification: read.
  • Delete Memory (delete_memory), Permanently delete a memory and its associated chunks and vector embeddings. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects5
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

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

Supported objects

ObjectReadWriteNotes
Create Space Yes No Create a new space or reuse an existing one. A space is a logical container for organizing related memories, configured with embedders that convert text to vector embeddings
Create Memory Yes No Store a document as a new memory in a space. The memory is processed asynchronously - chunked into searchable pieces and embedded into vectors. Accepts a file or plain text.
Retrieve Memories Yes No Perform similarity-based semantic retrieval across one or more spaces. Returns matching chunks ranked by relevance, with optional full memory definitions.
Get Memory Yes No Fetch a specific memory record by its ID, including metadata, processing status, and optionally the original content.
Delete Memory Yes No Permanently delete a memory and its associated chunks and vector embeddings.

Setup

Setup

  1. Add the GoodMem 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:
  • Base URL (baseUrl), required.
  • API Key (apiKey), required; stored as a sensitive connection value.
  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-goodmem@0.0.5; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required GoodMem 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-goodmem@0.0.5 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