adobe-webhooks-events
Implement Adobe I/O Events webhook registration, RSA-SHA256 signature verification, challenge handshake, and event-driven architectures with Creative Cloud, Experience Platform, and Firefly Services events. Trigger with phrases like "adobe webhook", "adobe events", "adobe I/O events", "adobe event registration", "adobe notifications".
Best use case
adobe-webhooks-events is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Adobe I/O Events webhook registration, RSA-SHA256 signature verification, challenge handshake, and event-driven architectures with Creative Cloud, Experience Platform, and Firefly Services events. Trigger with phrases like "adobe webhook", "adobe events", "adobe I/O events", "adobe event registration", "adobe notifications".
Teams using adobe-webhooks-events should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adobe-webhooks-events/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adobe-webhooks-events Compares
| Feature / Agent | adobe-webhooks-events | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement Adobe I/O Events webhook registration, RSA-SHA256 signature verification, challenge handshake, and event-driven architectures with Creative Cloud, Experience Platform, and Firefly Services events. Trigger with phrases like "adobe webhook", "adobe events", "adobe I/O events", "adobe event registration", "adobe notifications".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Adobe Webhooks & Events
## Overview
Implement Adobe I/O Events webhook endpoints with proper challenge-response handshake, RSA-SHA256 digital signature verification, and event routing for Creative Cloud Libraries, Experience Platform, and Firefly Services events.
## Prerequisites
- Adobe Developer Console project with Events API enabled
- HTTPS endpoint accessible from the internet
- `@adobe/aio-lib-events` installed (optional, for SDK approach)
- Understanding of Adobe I/O Events architecture
## Instructions
### Step 1: Register Webhook via Adobe I/O Events API
```typescript
// Register a webhook endpoint programmatically
import { getAccessToken } from '../adobe/client';
interface EventRegistration {
name: string;
description: string;
webhookUrl: string;
eventsOfInterest: Array<{
provider_id: string; // Event provider (e.g., Creative Cloud)
event_code: string; // Specific event type
}>;
deliveryType: 'webhook' | 'webhook_batch';
}
export async function registerWebhook(reg: EventRegistration): Promise<any> {
const token = await getAccessToken();
const response = await fetch(
`https://api.adobe.io/events/${process.env.ADOBE_IMS_ORG_ID}/integrations/${process.env.ADOBE_INTEGRATION_ID}/registrations`,
{
method: 'POST',
headers: {
'Authorization': `Bearer ${token}`,
'x-api-key': process.env.ADOBE_CLIENT_ID!,
'Content-Type': 'application/json',
},
body: JSON.stringify({
client_id: process.env.ADOBE_CLIENT_ID,
name: reg.name,
description: reg.description,
webhook_url: reg.webhookUrl,
events_of_interest: reg.eventsOfInterest,
delivery_type: reg.deliveryType || 'webhook',
}),
}
);
if (!response.ok) throw new Error(`Registration failed: ${await response.text()}`);
return response.json();
}
// Example: Register for Creative Cloud Library events
await registerWebhook({
name: 'CC Library Updates',
description: 'Track Creative Cloud Library changes',
webhookUrl: 'https://api.yourapp.com/webhooks/adobe',
eventsOfInterest: [
{ provider_id: 'ccstorage', event_code: 'library_create' },
{ provider_id: 'ccstorage', event_code: 'library_update' },
{ provider_id: 'ccstorage', event_code: 'library_delete' },
],
deliveryType: 'webhook',
});
```
### Step 2: Implement Challenge-Response Handshake
When registering a webhook, Adobe sends a `GET` request with a `challenge` query parameter. Your endpoint must respond with the challenge value:
```typescript
import express from 'express';
const app = express();
app.get('/webhooks/adobe', (req, res) => {
// Adobe challenge verification during registration
const challenge = req.query.challenge as string;
if (challenge) {
console.log('Adobe webhook challenge received');
return res.status(200).json({ challenge });
}
res.status(400).json({ error: 'Missing challenge parameter' });
});
```
### Step 3: Verify RSA-SHA256 Digital Signatures
Adobe I/O Events uses RSA-SHA256 (not HMAC). Public keys are served from `static.adobeioevents.com`:
```typescript
import crypto from 'crypto';
const publicKeyCache = new Map<string, string>();
async function fetchPublicKey(keyPath: string): Promise<string> {
if (publicKeyCache.has(keyPath)) return publicKeyCache.get(keyPath)!;
const res = await fetch(`https://static.adobeioevents.com${keyPath}`);
if (!res.ok) throw new Error(`Failed to fetch Adobe public key: ${res.status}`);
const key = await res.text();
publicKeyCache.set(keyPath, key);
return key;
}
async function verifyAdobeSignature(rawBody: Buffer, headers: Record<string, string>): Promise<boolean> {
for (const idx of ['1', '2']) {
const sig = headers[`x-adobe-digital-signature-${idx}`];
const keyPath = headers[`x-adobe-public-key${idx}-path`];
if (!sig || !keyPath) continue;
try {
const publicKey = await fetchPublicKey(keyPath);
const verifier = crypto.createVerify('RSA-SHA256');
verifier.update(rawBody);
if (verifier.verify(publicKey, sig, 'base64')) return true;
} catch (err) {
console.warn(`Adobe signature-${idx} verification error:`, err);
}
}
return false;
}
```
### Step 4: Event Handler with Routing
```typescript
// POST handler for incoming events
app.post('/webhooks/adobe',
express.raw({ type: 'application/json' }),
async (req, res) => {
// Verify signature
if (!await verifyAdobeSignature(req.body, req.headers as any)) {
console.error('Invalid Adobe webhook signature');
return res.status(401).json({ error: 'Invalid signature' });
}
const event = JSON.parse(req.body.toString());
// Route by event type
try {
await routeAdobeEvent(event);
res.status(200).json({ received: true });
} catch (error: any) {
console.error('Event processing failed:', error);
res.status(500).json({ error: error.message });
}
}
);
// Event type definitions
type AdobeEventType =
| 'library_create'
| 'library_update'
| 'library_delete'
| 'asset_created'
| 'asset_updated';
interface AdobeEvent {
event_id: string;
event: {
type: AdobeEventType;
activitystreams?: any;
xdmEntity?: any;
};
recipient_client_id: string;
}
const eventHandlers: Partial<Record<AdobeEventType, (event: AdobeEvent) => Promise<void>>> = {
library_create: async (event) => {
console.log('New CC Library created:', event.event_id);
// Sync library metadata to your database
},
library_update: async (event) => {
console.log('CC Library updated:', event.event_id);
// Refresh cached library data
},
library_delete: async (event) => {
console.log('CC Library deleted:', event.event_id);
// Remove from local cache/database
},
};
async function routeAdobeEvent(event: AdobeEvent): Promise<void> {
const handler = eventHandlers[event.event.type];
if (handler) {
await handler(event);
} else {
console.log(`Unhandled Adobe event type: ${event.event.type}`);
}
}
```
### Step 5: Idempotency (Prevent Duplicate Processing)
```typescript
import { Redis } from 'ioredis';
const redis = new Redis(process.env.REDIS_URL);
async function processEventIdempotently(event: AdobeEvent): Promise<boolean> {
const key = `adobe:event:${event.event_id}`;
// SET NX with 7-day TTL — returns null if key already exists
const result = await redis.set(key, '1', 'EX', 86400 * 7, 'NX');
if (!result) {
console.log(`Duplicate Adobe event skipped: ${event.event_id}`);
return false; // Already processed
}
await routeAdobeEvent(event);
return true;
}
```
## Output
- Webhook registered with Adobe I/O Events
- Challenge-response handshake handler for registration
- RSA-SHA256 signature verification with key caching
- Event routing by type with handler pattern
- Idempotency via Redis to prevent duplicate processing
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Challenge response 400 | Missing JSON content-type | Return `{ challenge }` as JSON |
| Signature always invalid | Not using raw body | Use `express.raw()` before parsing |
| Events not arriving | Registration failed | Check I/O Events dashboard for status |
| Duplicate events | No idempotency | Track `event_id` in Redis/DB |
| Public key fetch fails | Network/firewall | Whitelist `static.adobeioevents.com` |
## Resources
- [Adobe I/O Events Webhooks Guide](https://developer.adobe.com/events/docs/guides/)
- [I/O Events Registration API](https://developer.adobe.com/events/docs/guides/api/registration-api)
- [Signature Verification SDK](https://developer.adobe.com/events/docs/guides/sdk/sdk_signature_verification/)
- [CC Libraries Events](https://developer.adobe.com/creative-cloud-libraries/docs/integrate/guides/configuring-events-webhooks/)
## Next Steps
For performance optimization, see `adobe-performance-tuning`.Related Skills
server-sent-events-setup
Server Sent Events Setup - Auto-activating skill for API Integration. Triggers on: server sent events setup, server sent events setup Part of the API Integration skill category.
exa-webhooks-events
Build event-driven integrations with Exa using scheduled monitors and content alerts. Use when building content monitoring, competitive intelligence pipelines, or scheduled search automation with Exa. Trigger with phrases like "exa monitor", "exa content alerts", "exa scheduled search", "exa event-driven", "exa notifications".
evernote-webhooks-events
Implement Evernote webhook notifications and sync events. Use when handling note changes, implementing real-time sync, or processing Evernote notifications. Trigger with phrases like "evernote webhook", "evernote events", "evernote sync", "evernote notifications".
emitting-api-events
Build event-driven APIs with webhooks, Server-Sent Events, and real-time notifications. Use when building event-driven API architectures. Trigger with phrases like "add webhooks", "implement events", or "create event-driven API".
elevenlabs-webhooks-events
Implement ElevenLabs webhook HMAC signature verification and event handling. Use when setting up webhook endpoints for transcription completion, call recording, or agent conversation events from ElevenLabs. Trigger: "elevenlabs webhook", "elevenlabs events", "elevenlabs webhook signature", "handle elevenlabs notifications", "elevenlabs post-call webhook", "elevenlabs transcription webhook".
documenso-webhooks-events
Implement Documenso webhook configuration and event handling. Use when setting up webhook endpoints, handling document events, or implementing real-time notifications for document signing. Trigger with phrases like "documenso webhook", "documenso events", "document completed webhook", "signing notification".
deepgram-webhooks-events
Implement Deepgram callback and webhook handling for async transcription. Use when implementing callback URLs, processing async transcription results, or handling Deepgram event notifications. Trigger: "deepgram callback", "deepgram webhook", "async transcription", "deepgram events", "deepgram notifications", "deepgram async".
databricks-webhooks-events
Configure Databricks job notifications, webhooks, and event handling. Use when setting up Slack/Teams notifications, configuring alerts, or integrating Databricks events with external systems. Trigger with phrases like "databricks webhook", "databricks notifications", "databricks alerts", "job failure notification", "databricks slack".
customerio-webhooks-events
Implement Customer.io webhook and reporting event handling. Use when processing email delivery events, click/open tracking, bounce handling, or streaming to a data warehouse. Trigger: "customer.io webhook", "customer.io events", "customer.io delivery status", "customer.io bounces", "customer.io open tracking".
coreweave-webhooks-events
Monitor CoreWeave cluster events and GPU workload status. Use when tracking pod lifecycle events, monitoring GPU utilization, or alerting on inference service health changes. Trigger with phrases like "coreweave events", "coreweave monitoring", "coreweave pod alerts", "coreweave gpu monitoring".
cohere-webhooks-events
Implement Cohere streaming event handling, SSE patterns, and connector webhooks. Use when building streaming UIs, handling chat/tool events, or registering Cohere connectors for RAG. Trigger with phrases like "cohere streaming", "cohere events", "cohere SSE", "cohere connectors", "cohere webhook".
coderabbit-webhooks-events
Implement CodeRabbit webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling CodeRabbit event notifications securely. Trigger with phrases like "coderabbit webhook", "coderabbit events", "coderabbit webhook signature", "handle coderabbit events", "coderabbit notifications".