Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Instabase

Integrate with Instabase AI Hub to automate document processing and AI workflows

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

Overview

Connect Instabase with Flows360

Integrate with Instabase AI Hub to automate document processing and AI workflows

Use the Instabase 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 3 actions and 1 trigger.

Available actions

  • Create Conversation and Upload Files
  • Converse with Document
  • Custom API Call

Available triggers

  • New Conversation

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: Instabase
  • Package: @activepieces/piece-instabase@0.2.0
  • Exact artifact digest: sha256:a5c22a76d1d285908b2f9d30b786f601b45a7f654cb0b626daadac6b16ff6ea4
  • 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 Conversation and Upload Files (create_conversation), Create a new conversation and upload files to it Classification: read.
  • Converse with Document (converse_with_document), Ask a question about a document in a conversation Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Conversation, 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 objects4
Supported actions3
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential
  • IB Context Optional
  • API Root URL Required

Supported objects

ObjectReadWriteNotes
Create Conversation and Upload Files Yes No Create a new conversation and upload files to it
Converse with Document Yes No Ask a question about a document in a conversation
Custom API Call Yes No Make a custom API call to a specific endpoint
New Conversation Yes No polling trigger declared by the pinned package.

Supported actions

Create Conversation and Upload Files · Read

Create a new conversation and upload files to it

create_conversation · Risk: low · Retry: safe

Inputs

  • name · string · Optional, Name of the conversation
  • description · string · Optional, Description of the conversation
  • files · array · Required, Files to upload to the conversation
  • org · string · Optional, Organization ID (for organization accounts)
  • workspace · string · Optional, Workspace name where the conversation is created
  • enable_object_detection · boolean · Optional, Enable object detection for extracting tables and checkboxes
  • enable_entity_detection · boolean · Optional, Enable entity detection for signatures and barcodes
  • write_converted_image · boolean · Optional, Save image files generated when processing documents
  • write_thumbnail · boolean · Optional, Generate and save thumbnails of processed documents
  • fast_mode · boolean · Optional, Skip preprocessing steps for faster processing
  • enable_multilanguage_support · boolean · Optional, Enable support for non-Latin languages
  • enable_multilanguage_advanced_mode · boolean · Optional, Enable advanced support for complex non-Latin languages
Converse with Document · Read

Ask a question about a document in a conversation

converse_with_document · Risk: low · Retry: safe

Inputs

  • conversation_id · string · Required, Select the conversation
  • question · string · Required, The question to ask the document
  • document_ids · array · Required, Select the documents to query
  • mode · string · Optional, The model to use to answer the question
  • fast_mode · boolean · Optional, Enable fast mode for quicker responses
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

New Conversation · Poll

Triggers when a new conversation is created

Setup

Setup

  1. Add the Instabase 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 Token (apiToken), required; stored as a sensitive connection value.
  • IB Context (ibContext), optional.
  • API Root URL (apiRoot), required.
  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-instabase@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 1 trigger 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 Instabase 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-instabase@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