[APP] EventDock

**Name of app / service**

EventDock — https://eventdock.app

Webhook reliability platform: receives webhooks from any provider (Stripe, Shopify, GitHub, Twilio, Paddle, or generic), verifies the signature, and delivers them to your endpoint with automatic retries, a dead-letter queue, replay, and delivery monitoring.

**Link to developer documentation**

- API docs: https://eventdock.app/docs
- API base URL: `https://api.eventdock.app`
- Auth: API key as a Bearer token — `Authorization: Bearer evdk_...`. Users find their key in the EventDock dashboard under Settings → API Keys.
- Suggested credential-validation endpoint: `GET https://api.eventdock.app/v1/endpoints` (returns 200 + JSON list with a valid key, 401 otherwise)
- Logo: https://eventdock.app/logo.svg (PNG: https://eventdock.app/logo.png)
- Free tier for testing, no card required: https://dashboard.eventdock.app (magic-link email auth)

**Is lack of support preventing you from moving forward, or do you have a workaround?**

Yes — it's blocking a component PR that's already written and reviewed. PR #21128 ("New Components - eventdock") adds the app file plus a `reliable-http-forward` action; CodeRabbit's review comments were addressed back in June. @ashwins01 let me know the PR can't be reviewed or tested until the EventDock app integration exists in Pipedream, and asked me to raise this request here rather than via the integrations mailbox (which is currently backed up).

There's no real workaround today: users can hit the EventDock API from a generic HTTP request step, but they then have to paste and manage the API key by hand in every workflow instead of using a managed Pipedream connection.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

The PR already implements the first action; the rest are natural follow-ups once the app exists:

- **Action — Reliable HTTP Forward** (in PR #21128): send a payload through EventDock so delivery is retried automatically instead of being lost when the destination is briefly down.
- **Action — Create Endpoint**: provision an EventDock ingest endpoint from a workflow.
- **Trigger — New Event Received**: emit when EventDock receives a webhook, so a Pipedream workflow runs on reliably-delivered events (with retries/DLQ handled upstream).
- **Trigger — Delivery Failed**: emit when an event exhausts retries and lands in the dead-letter queue — useful for alerting.

Happy to supply test credentials or make any changes the integrations team wants. Related PR: https://github.com/PipedreamHQ/pipedream/pull/21128

Review PR #21128, especially its EventDock app file and reliable-http-forward action, then compare the integration with the supplied API documentation and credential-validation endpoint. Done means the EventDock connection and first action are available in Pipedream and the existing PR can be tested and reviewed.

Written by the indexing model from the issue text.