Individual skill

palantir-webhooks-events

Choose and implement a supported Foundry event path using OSDK object subscriptions, direct WebSocket subscriptions, monitoring webhooks, or Data Connection webhooks. Use when reacting to object or monitoring changes. Trigger with "Palantir events" or "Foundry subscription".

plugins/saas-packs/palantir-pack/skills/palantir-webhooks-events/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Palantir Event and Subscription Integration

## Overview

Start from the event producer and delivery guarantee: real-time Ontology object updates use OSDK or Object Set Watcher WebSocket subscriptions, while monitoring notifications and outbound integrations use their documented webhook surfaces. Never invent a general `ontology.object.created` registration API.

## Prerequisites

- Identify the producer, consumer, object set or monitoring view, supported delivery surface, data sensitivity, latency objective, and recovery behavior.
- Confirm the generated OSDK version or direct WebSocket contract, or the configured Data Connection webhook required by monitoring.
- Read `references/official-docs.md` and verify target-enrollment feature access.
- Prepare a non-production object set or monitoring view and an idempotent consumer.

## Current Contract
Back to top