Download for MacApple silicon, macOS 14+
Skill

remote-api-webhooks

@remoteoss Updated 2026-07-09

Receive and verify Remote.com webhooks in an integration. Use when subscribing to events (POST /v1/webhook-callbacks), building a receiver, verifying the X-Remote-Signature HMAC, parsing the flat event payload, deduping/idempotency, or choosing which event_type to listen for. Covers HMAC-SHA256 hex over raw_body + ':' + millisecond timestamp. Do NOT use to operate via the MCP, for auth (remote-api-auth), outbound API calls (remote-api-integration), or form writes/onboarding (remote-api-forms / remote-api-onboarding).

Install

With your agent

Install OMGSkills skill "remoteoss/remote-for-ai:skills/remote-api-webhooks" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/remoteoss/remote-for-ai /tmp/remote-for-ai && ln -s /tmp/remote-for-ai/skills/remote-api-webhooks ~/.claude/skills/remote-api-webhooks

From README

Remote API Webhooks Covers the full lifecycle of receiving Remote.com webhook events in an integration: subscribing to event types, building a secure receiver endpoint, verifying the HMAC-SHA256 signature, parsing the flat event payload, handling retries idempotently, and managing subscriptions over time. Invoke This Skill When Subscribing to Remote webhook events (POST /v1/webhook-callbacks). Building a receiver endpoint that accepts inbound deliveries. Verifying the X-Remote-Signature HMAC before trusting a payload. Parsing the flat event envelope and branching on eventtype. Deduplicating retried deliveries or implementing idempotency guards. Choosing which eventtype values to listen for. Managing an existing subscription: updating events, listing delivery history, or deleting the callback. Not for operating your Remote workspace via the MCP server. Prerequisites An access token with sufficient scopes to call POST /v1/webhook-callbacks — see remote-api-auth for how to obtain one.