Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Webhook

Receive HTTP requests and trigger flows using unique URLs.

CategoryCore
AuthenticationNo authentication required
Version0.1.41
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Webhook with Flows360

Receive HTTP requests and trigger flows using unique URLs.

Use the Webhook 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 2 actions and 1 trigger.

Available actions

  • Return Response
  • Respond and Wait for Next Webhook

Available triggers

  • Catch Webhook

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: Webhook
  • Package: @activepieces/piece-webhook@0.1.41
  • Exact artifact digest: sha256:94086b8e5eef9f6a70aef579ff5a0761ff4df78243a239d4e6b7ebb4f6a95bd9
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

No connection authentication is declared by the package. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Return Response (return_response), return a response Classification: read.
  • Respond and Wait for Next Webhook (return_response_and_wait_for_next_webhook), return a response and wait for the next webhook to resume the flow Classification: read.

Trigger contracts

  • Catch Webhook, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationNo authentication required
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: No authentication required

Supported objects

ObjectReadWriteNotes
Return Response Yes No return a response
Respond and Wait for Next Webhook Yes No return a response and wait for the next webhook to resume the flow
Catch Webhook Yes No webhook trigger declared by the pinned package.

Supported actions

Return Response · Read

return a response

return_response · Risk: low · Retry: safe

Inputs

  • responseType · string · Optional
  • fields · object · Required
  • respond · string · Optional
Respond and Wait for Next Webhook · Read

return a response and wait for the next webhook to resume the flow

return_response_and_wait_for_next_webhook · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, **Respond and Wait for Next Webhook** n Check the response header (x-activepieces-resume-webhook-url) for the next webhook URL and call it to resume the flow. n
  • responseType · string · Optional
  • fields · object · Required

Triggers

Catch Webhook · Webhook

Receive incoming HTTP/webhooks using any HTTP method such as GET, POST, PUT, DELETE, etc.

Inputs

  • liveMarkdown · string
  • syncMarkdown · string
  • testMarkdown · string
  • authType · string
  • authFields · object

Setup

Setup

  1. Add the Webhook 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-webhook@0.1.41; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Webhook 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-webhook@0.1.41 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