Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Griptape Cloud

Griptape Cloud integration for Flows360 workflows.

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

Overview

Connect Griptape Cloud with Flows360

Griptape Cloud integration for Flows360 workflows.

Use the Griptape Cloud 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 4 triggers.

Available actions

  • Create Assistant Run
  • Create Structure Run
  • Get Assistant Run
  • Get Structure Run
  • Custom API Call

Available triggers

  • Assistant Run Completes
  • Assistant Run Succeeds
  • Structure Run Completes
  • Structure Run Succeeds

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: Griptape Cloud
  • Package: @activepieces/piece-griptape@0.2.0
  • Exact artifact digest: sha256:f6fb3cc188d53b568fccae87bf800e647a16fcc4cae95e3e509cf5e5909d0069
  • 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 Assistant Run (createAssistantRun), Create a run for an assistant with optional additional resources Classification: read.
  • Create Structure Run (createStructureRun), Create a run for a structure and wait for completion Classification: read.
  • Get Assistant Run (getAssistantRun), Get details of a specific assistant run Classification: read.
  • Get Structure Run (getStructureRun), Get details of a specific structure run Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Assistant Run Completes, polling.
  • Assistant Run Succeeds, polling.
  • Structure Run Completes, polling.
  • Structure Run Succeeds, 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 objects9
Supported actions5
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Assistant Run Yes No Create a run for an assistant with optional additional resources
Create Structure Run Yes No Create a run for a structure and wait for completion
Get Assistant Run Yes No Get details of a specific assistant run
Get Structure Run Yes No Get details of a specific structure run
Custom API Call Yes No Make a custom API call to a specific endpoint
Assistant Run Completes Yes No polling trigger declared by the pinned package.
Assistant Run Succeeds Yes No polling trigger declared by the pinned package.
Structure Run Completes Yes No polling trigger declared by the pinned package.
Structure Run Succeeds Yes No polling trigger declared by the pinned package.

Supported actions

Create Assistant Run · Read

Create a run for an assistant with optional additional resources

create_assistant_run · Risk: low · Retry: safe

Inputs

  • assistant_id · string · Required, Select the assistant
  • input · string · Required, Input to provide to the assistant
  • knowledgeBaseIds · array · Optional, Select knowledge bases to use
  • rulesets · array · Optional, Select rulesets to apply
  • structures · array · Optional, Select structures to use
  • tools · array · Optional, Select tools to use
  • thread · array · Optional, Select the thread
  • create_new_thread · boolean · Optional, Create a new thread for this run
Create Structure Run · Read

Create a run for a structure and wait for completion

create_structure_run · Risk: low · Retry: safe

Inputs

  • structure_id · string · Required, Select the structure
  • input_args · array · Required, Input arguments for the structure run
Get Assistant Run · Read

Get details of a specific assistant run

get_assistant_run · Risk: low · Retry: safe

Inputs

  • assistant_id · string · Required, Select the assistant
  • assistant_run_id · string · Required, Select the assistant run
Get Structure Run · Read

Get details of a specific structure run

get_structure_run · Risk: low · Retry: safe

Inputs

  • structure_id · string · Required, Select the structure
  • structure_run_id · string · Required, Select the structure run
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Assistant Run Completes · Poll

Trigger when an assistant run is completed (succeeded, failed, or cancelled)

Inputs

  • assistant_id · string
Assistant Run Succeeds · Poll

Trigger when an assistant run succeeds

Inputs

  • assistant_id · string
Structure Run Completes · Poll

Inputs

  • structure_id · string
Structure Run Succeeds · Poll

Inputs

  • structure_id · string

Setup

Setup

  1. Add the Griptape Cloud 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-griptape@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 4 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 Griptape Cloud 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-griptape@0.2.0 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