Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

AnyHook Websocket

AnyHook Websocket enables real-time communication through AnyHook proxy server by allowing you to subscribe and listen to websocket events

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 26, 2026

Overview

Connect AnyHook Websocket with Flows360

AnyHook Websocket enables real-time communication through AnyHook proxy server by allowing you to subscribe and listen to websocket events

Use the AnyHook Websocket 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 no declared actions and 1 trigger.

Available actions

  • No actions are declared in this pinned package.

Available triggers

  • New Websocket Subscription Event

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: AnyHook Websocket
  • Package: @activepieces/piece-anyhook-websocket@0.1.7
  • Exact artifact digest: sha256:580b19ce5fcd850fa918a18381cff6368dd34fabf3b9654d462be2ab596aa699
  • 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

No actions are declared by this package version.

Trigger contracts

  • New Websocket Subscription Event, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 0 exercised action entrypoints and 1 exercised trigger entrypoint.

Capability summary

Authenticationcustom
Supported objects1
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • AnyHook Server URL Required

Supported objects

ObjectReadWriteNotes
New Websocket Subscription Event Yes No webhook trigger declared by the pinned package.

Triggers

New Websocket Subscription Event · Webhook

Triggers on a new Websocket subscription event

Inputs

  • websocketUrl · string
  • headers · object
  • message · object

Setup

Setup

  1. Add the AnyHook Websocket 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:
  • AnyHook Server URL (proxyBaseUrl), 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-anyhook-websocket@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 0 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 0 exercised action entrypoints and 1 exercised trigger entrypoint.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required AnyHook Websocket 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-anyhook-websocket@0.1.7 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