Set up the route. Protect the URL. Test one event.

Basic setup

1. Add FlowIngressAdd the FlowIngress — Incoming webhook starter to the Google Workspace Studio flow you want the external event to start.
2. Authorize & get webhook URLAuthorize once for that configuration and obtain its unique opaque webhook URL.
3. Copy the opaque webhook URLUse the generated route as the HTTPS POST target. Treat the complete URL as a credential.
4. Configure the external senderSet the external system to send an HTTPS POST to the generated route.
5. Confirm the flow runsSend a test event and confirm the configured Workspace Studio flow starts and receives the expected event values.

Test request

curl -X POST "https://<your-flowingress-webhook>"   -H "Content-Type: application/json"   -d '{"event":"test"}'

Values available to the flow

• Raw request body(rawBody) — incoming request body.
• Unique event identifier(eventId) — identifier generated for the event.
• Received at(receivedAt) — receive timestamp.

Rotate webhook URL

If the webhook URL may have been exposed, useRotate webhook URL. Rotation immediately invalidates the previous URL and creates a different replacement URL.

Update each legitimate sender to use the replacement URL. Requests to the previous URL are rejected after rotation.

Disconnect this webhook

Use Disconnect this webhook when you want to terminate the FlowIngress authorization and route for that configuration.

Disconnect removes the stored FlowIngress refresh-token authorization for that configuration and invalidates its webhook route.

Disconnect is terminal for that configuration in the current MVP. To reconnect, create a new FlowIngress — Incoming webhook starter configuration and use Authorize & get webhook URLagain. Same-configuration reauthorization is not supported.

Webhook credential handling

Do not publish the webhook URL, put it in a public repository, expose it in screenshots, or paste it into a support message. Do not send the webhook URL to support.

Do not send OAuth credentials, refresh tokens, management credentials or other secrets to support.

Basic troubleshooting

The sender receives a route error

Confirm the complete URL was copied correctly. Unknown routes are rejected. If the webhook was rotated, confirm the sender is using the replacement URL rather than the invalidated previous URL.

The event is sent but the flow does not start

Confirm the sender used HTTPS POST, the intended Workspace Studio flow still contains the FlowIngress starter, and the configuration has not been disconnected.

The flow starts but the data is unexpected

Inspect rawBody, eventId andreceivedAt in the flow. Confirm the external sender is sending the body and content type you expect.

Contact support

Emailhello@finnstackgroup.com.

Include a concise description of the problem and non-secret error context. Do not include webhook URLs, OAuth credentials, management credentials or other secrets.