Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Visible

Visible integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.0.9
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Visible with Flows360

Visible integration for Flows360 workflows.

Use the Visible 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 no declared triggers.

Available actions

  • Create Portfolio Company
  • Create or Update Contact
  • Create Metric
  • Custom API Call

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: Visible
  • Package: @activepieces/piece-visible@0.0.9
  • Exact artifact digest: sha256:d413a0abacf57ed4fe8ea4c3efe4f89530c2526c89e0c0b159488be05dbd6d19
  • 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 Portfolio Company (create_portfolio_company), Creates a new portfolio company. Classification: read.
  • Create or Update Contact (create_or_update_contact), Creates a contact (or updates contact based on email address). Classification: read.
  • Create Metric (create_metric), Create a new metric for a company. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to any Visible endpoint 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 objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Portfolio Company Yes No Creates a new portfolio company.
Create or Update Contact Yes No Creates a contact (or updates contact based on email address).
Create Metric Yes No Create a new metric for a company.
Custom API Call Yes No Make a custom API call to any Visible endpoint

Supported actions

Create Portfolio Company · Read

Creates a new portfolio company.

create_portfolio_company · Risk: low · Retry: safe

Inputs

  • companyId · string · Required
  • name · string · Required
  • websiteUrl · string · Optional
  • currency · string · Optional
  • primaryContactId · string · Optional
Create or Update Contact · Read

Creates a contact (or updates contact based on email address).

create_or_update_contact · Risk: low · Retry: safe

Inputs

  • email · string · Required
  • companyId · string · Required
  • firstName · string · Optional
  • lastName · string · Optional
  • title · string · Optional
  • contactListIds · array · Optional
Create Metric · Read

Create a new metric for a company.

create_metric · Risk: low · Retry: safe

Inputs

  • companyId · string · Required
  • name · string · Required
  • frequency · string · Required
  • unit · string · Required
Custom API Call · Read

Make a custom API call to any Visible endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Required, Authorization headers are injected automatically from your connection.
  • queryParams · object · Required
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional
  • timeout · number · Optional
  • followRedirects · boolean · Optional

Setup

Setup

  1. Add the Visible 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-visible@0.0.9; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 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 Visible 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-visible@0.0.9 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