Web Requests and Webhooks

GetMyBot integrates with external systems over HTTP in both directions: incoming requests trigger reactions, while outgoing actions call third-party APIs. This connects your bot to CRMs, payment systems, website forms, and any other services.

Incoming webhook (trigger)

The "Incoming web request (webhook)" trigger fires a reaction on an external HTTP request:

  • Path — the receiver address (the full URL is formed from the bot address and the path).
  • Secret token — protects the endpoint from unauthorized access.
  • Method — POST / GET / PUT / ANY.

Request data (form fields or body) enters the execution context and is available in actions via {{ctx.field}}. This lets a website or service "push" an event to the bot — for example, payment confirmed → send the user their access.

Outgoing web request (action)

The "Web request" action makes an HTTP request from a reaction:

  • method (GET/POST/PUT/DELETE), headers, body (JSON or form);
  • success codes, timeout, and retry count on error;
  • saving the response to a parameter or ctx via JSONPath;
  • async mode (do not block the reaction) and triggering reactions on success / on error.

Related actions: "Load URL" (download page text into ctx) and "Query source" / "Write to source" for saved connectors — see Sources and keys.

Webhook integration

For regularly sending data to one service, it is more convenient to configure a Webhook integration (URL + HMAC signature) — see Integrations.

Security

Incoming endpoints are protected by a secret token; outgoing requests pass through SSRF protection (access to the internal network is blocked), and the response size is limited.

What's next