Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared
This commit is contained in:
@@ -69,7 +69,7 @@ without an inbound port. Replace `portal.example.com` with your portal's API
|
||||
address in these examples:
|
||||
|
||||
- A webhook or a served WebSocket:
|
||||
`https://portal.example.com/i/<instance-id>/hooks/<flow>/<url>/<secret>`,
|
||||
`https://portal.example.com/i/<instance-id>/hooks/<flow-id>/<url>/<secret>`,
|
||||
with `wss://` for a socket.
|
||||
- An agent: `https://portal.example.com/i/<instance-id>/mcp`, see
|
||||
[Agents over MCP](../code/agents.md).
|
||||
|
||||
Reference in New Issue
Block a user