Golem Add Webhook Effect

Using Webhooks in an Effect Golem Agent

Webhook.create allocates a Golem promise and mints a temporary public URL for it. Posting to the URL completes the promise; awaiting the handle durably suspends the current invocation without consuming compute until the callback arrives.

Use this for asynchronous provider callbacks such as payment, CI/CD, and workflow notifications. The URL is a one-shot rendezvous, not a permanent incoming HTTP endpoint. Use Http.post(...) instead when an external system needs a stable recurring route.

Prerequisites

The agent that calls Webhook.create must:

1. declare an HTTP mount with Http.mount(...); and
2. be included in the active httpApi deployment in golem.yaml.

Otherwise Webhook.create fails with WebhookHostError after allocating its underlying promise. The error type is exported from @golemcloud/effect-golem.

Related Skills

API

Import the SDK namespace rather than translating APIs from another language SDK:

import { Effect, Schema } from "effect";
import {
  FetchHttpClient,
  HttpClient,
  HttpClientRequest,
  HttpClientResponse,
} from "effect/unstable/http";
import { defineAgent, Http, method, Webhook } from "@golemcloud/effect-golem";

Create, Share, and Await

Keep the handle local when one handler creates the webhook and immediately awaits it:

const waitForCallback = Effect.gen(function* () {
  const handle = yield* Webhook.create;

  // Register handle.url with the external provider through the intended secure channel.

  const payload = yield* handle.await;
  return payload.text();
}).pipe(Effect.orDie);

Webhook.create and handle.await have typed host errors. If the public method does not declare matching error schemas, explicitly convert those infrastructure failures to defects with Effect.orDie; do not hide them by returning an empty payload.

For JSON, decode with an Effect Schema:

const PaymentEvent = Schema.Struct({
  id: Schema.String,
  status: Schema.String,
});

const registerWebhook = (callbackUrl: string) =>
  HttpClientRequest.post("https://provider.example.com/subscriptions").pipe(
    HttpClientRequest.bodyJson({ callbackUrl }),
    Effect.flatMap(HttpClient.execute),
    Effect.flatMap(HttpClientResponse.filterStatusOk),
    Effect.asVoid,
  );

payload.decode(PaymentEvent) validates both the JSON syntax and the decoded shape. Avoid payload.json<PaymentEvent>() when a parsing exception would escape the Effect error channel.

Mount and Webhook URL

Declare the ordinary agent mount and, optionally, a custom webhook suffix together:

export const PaymentWatcher = defineAgent({
  name: "PaymentWatcher",
  mode: "durable",
  id: {
    accountName: Schema.String,
  },
  http: Http.mount("/payments/{accountName}", {
    webhookSuffix: "/payment-callbacks/{accountName}",
  }),
  methods: {
    waitForPayment: method({
      input: {},
      success: PaymentEvent,
      http: [Http.post("/wait")],
    }),
  },
}).implement({
  init: () => Effect.void,
  methods: () => ({
    waitForPayment: () =>
      Effect.gen(function* () {
        const handle = yield* Webhook.create;
        yield* registerWebhook(handle.url);
        const payload = yield* handle.await;
        return yield* payload.decode(PaymentEvent);
      }).pipe(Effect.provide(FetchHttpClient.layer), Effect.orDie),
  }),
});

The generated URL has this shape:

https://<domain>/<webhook-prefix>/<webhook-suffix>/<signed-id>

• The deployment's webhookUrl controls the prefix and defaults to /webhooks.
• The suffix defaults to the agent type name in kebab-case.
• webhookSuffix accepts literal segments, constructor variables such as {accountName}, and system variables such as {agent-type}.
• Suffixes cannot contain query parameters or catch-all variables.

Deploy the agent without removing existing entries:

httpApi:
  deployments:
    local:
      - domain: payments.localhost:9006
        webhookUrl: "/callbacks/"
        agents:
          PaymentWatcher: {}

After golem build and golem deploy --yes, an external HTTP client completes a webhook by POSTing its payload directly to handle.url.

Sharing a URL with Another Agent

Use the typed client on an agent spec for same-component RPC:

const shareCallbackUrl = Effect.gen(function* () {
  const receiver = yield* CallbackRegistry.client.get({ accountName });
  yield* receiver.receiveUrl.trigger({ url: handle.url });
  return yield* handle.await;
});

Define receiveUrl with method({ input: { url: Schema.String }, ... }); remote methods and client.get(...) are Effects. Use the remote method's .trigger(...) form when URL handoff is fire-and-forget and the creator should enter handle.await immediately. A normal yield* receiver.receiveUrl(...) waits for the remote method to finish before reaching the webhook wait; use that form only when acknowledgement is required.

A separate agent can store or expose the URL while the webhook creator is suspended. For a real webhook integration, an external system must still POST to that URL.

Register the Callback over Outgoing HTTP

Use Effect's HTTP client when the agent must register the one-shot callback URL with an external provider. FetchHttpClient.layer executes through QuickJS's WASI-backed globalThis.fetch; do not replace it with a raw fetch wrapped in Effect.tryPromise.

const waitForProvider = Effect.gen(function* () {
  const handle = yield* Webhook.create;

  yield* registerWebhook(handle.url);

  const payload = yield* handle.await;
  return yield* payload.decode(PaymentEvent);
}).pipe(Effect.provide(FetchHttpClient.layer), Effect.orDie);

Request construction and JSON encoding are immutable Effect operations. Execute the request with HttpClient.execute, apply HttpClientResponse.filterStatusOk, and consume any response body the provider contract requires before awaiting the callback. Transport, status, and encoding failures remain in the Effect error channel; map expected failures to a declared method error or use Effect.orDie when they are infrastructure defects.

This outgoing request only registers or shares the callback URL. The provider must later POST its payload to handle.url; do not complete handle.promiseId directly as a substitute for exercising the signed webhook URL and its HTTP routing.

State and Lifecycle Rules

• Keep WebhookHandle invocation-local when creation and awaiting happen in one handler.
• A plain Ref may temporarily hold a handle, but never put a handle in snapshot state: its await and poll fields are Effects and are not schema-serializable.
• Snapshot only plain data such as the URL and result. This SDK revision cannot reconstruct a handle from a persisted promiseId.
• Only the creating agent may call handle.await, handle.poll, or the corresponding raw promise read operations. Another agent may complete a shared promise ID.
• The URL accepts a POST body only and completes one promise once.
• Treat the signed URL as a one-shot bearer capability: share it only with the intended caller and do not write it to application logs.
• Let Golem persist the suspension and replay. Do not add polling loops or manual retries around handle.await.
• Register every implemented agent module from src/main.ts with an emitted .js side-effect import, and do not edit files under golem-temp/.