Stripe
Verifies the Stripe-Signature header (HMAC-SHA256 over the timestamp and body) within a replay window.
These nodes ship with L2M and are configured in the studio, with credentials kept in the encrypted secret store. For everything else, attach an MCP server to an agent and govern its tools from the MCP control plane.
The pieces an agent is built from. Chat models attach to an agent's model slot; MCP tools and memory attach to its rings.
App nodes run one operation each, with app triggers where the vendor sends events.
Query and write data stores, call any HTTP API, and read rendered web pages.
Besides app triggers and webhooks, workflows start on a schedule, from a form or chat, from a stream or queue, or as a tool other MCP clients call.
App triggers verify the sender's signature scheme; the generic webhook supports bearer tokens and HMAC-SHA256 with a replay window.
Verifies the Stripe-Signature header (HMAC-SHA256 over the timestamp and body) within a replay window.
HMAC-SHA256 over the raw body, checked against X-Hub-Signature-256.
Signing-secret verification of X-Slack-Signature with a timestamp check.
Ed25519 signature verification with the application's public key.
Matches X-Telegram-Bot-Api-Secret-Token against the configured secret.
none, bearer_token or hmac_sha256 on any webhook_input, with optional idempotency keys.
Connect its MCP server and register it once: L2M probes it, tracks its tools and applies your policies. Or write a community node package with the node SDK.