Zapier

About

A Payload plugin that forwards collection change events to a Zapier webhook URL. When a document in a configured collection is created, updated, or deleted, the plugin fires an HTTP request to Zapier carrying the collection slug, the operation, and the document data, so downstream Zaps can react to Payload content changes. The plugin works by registering `afterChange` and `afterDelete` hooks on the targeted collections. The HTTP method follows the operation: POST for create, PUT for update, DELETE for delete. The request body is a JSON object with `collectionSlug`, `operation`, and `data` fields, which pairs well with Zapier Paths to branch on collection and operation. Configuration takes a `collections` array of slugs (or `["*"]` to cover every collection), the required `webhookURL`, and an optional `enabled` predicate. `enabled` can be a static boolean or an async function that receives the hook arguments plus the operation, letting you gate Zaps on request context such as the current user's role. This targets Payload v1 (peer dependency `payload ^1.1.11`) and imports collection hook types from Payload's internal `dist` paths, so it has not been updated for the Payload v3 plugin API. It is a thin, generic integration with no admin UI or persisted state.

Package info

Package name

@payloadcms/plugin-zapier

Latest version

0.0.9

Unpacked size

18 kB

License

MIT

Weekly downloads

29

Last publish

Oct 14, 2022