Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Medullar

AI-powered discovery & insight platform that acts as your extended digital mind

CategoryArtificial Intelligence
Authenticationcustom
Version0.3.6
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Medullar with Flows360

AI-powered discovery & insight platform that acts as your extended digital mind

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

Available actions

  • Create new Space
  • List Spaces
  • Add Space Record
  • Ask Space
  • Delete Space
  • Rename Space

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: Medullar
  • Package: @activepieces/piece-medullar@0.3.6
  • Exact artifact digest: sha256:90ee4d0a40339c775ca25afbbf5055c4416abab05d121110d72d706ed884e4cf
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. 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 new Space (createSpace), Create a new Space. Classification: read.
  • List Spaces (listSpaces), List all user Spaces Classification: read.
  • Add Space Record (addSpaceRecord), Adds a Record into a Space Classification: read.
  • Ask Space (askSpace), Ask anything to a Space Classification: read.
  • Delete Space (deleteSpace), Delete an existing Space. Classification: read.
  • Rename Space (renameSpace), Rename an existing Space. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

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 actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create new Space Yes No Create a new Space.
List Spaces Yes No List all user Spaces
Add Space Record Yes No Adds a Record into a Space
Ask Space Yes No Ask anything to a Space
Delete Space Yes No Delete an existing Space.
Rename Space Yes No Rename an existing Space.

Supported actions

Create new Space · Read

Create a new Space.

create_space · Risk: low · Retry: safe

Inputs

  • space_name · string · Required
List Spaces · Read

List all user Spaces

list_spaces · Risk: low · Retry: safe

Add Space Record · Read

Adds a Record into a Space

add_space_record · Risk: low · Retry: safe

Inputs

  • spaceId · string · Required, Select an Space
  • sourceType · string · Required, Select source type
  • content · string · Optional, Optional. Content of the record
  • url · string · Optional, Optional. URL of the record
Ask Space · Read

Ask anything to a Space

ask_space · Risk: low · Retry: safe

Inputs

  • spaceId · string · Required, Select an Space
  • chatId · string · Optional, Optional. Select a Chat where messages will be stored, if not selected, a default chat will be created with the name `automated`
  • selectedMode · string · Required, Select chat mode.
  • isReasoning · boolean · Optional, Optional. Enable Deep Analysis to get more accurate results but slower response time
  • text · string · Required, Message to send to the Space
Delete Space · Read

Delete an existing Space.

delete_space · Risk: low · Retry: safe

Inputs

  • spaceId · string · Required, Select an Space
Rename Space · Read

Rename an existing Space.

rename_space · Risk: low · Retry: safe

Inputs

  • spaceId · string · Required, Select an Space
  • space_name · string · Required

Setup

Setup

  1. Add the Medullar 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:
  • No provider credential fields are declared by the pinned package.
  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-medullar@0.3.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 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.
  • 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 Medullar 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-medullar@0.3.6 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