[APP] DocSpring

**Name of app / service**

DocSpring — https://docspring.com — a PDF generation & e-signature API.

**Link to developer documentation**

- Docs: https://docspring.com/docs
- Authentication: HTTP Basic auth using an API token — a **token ID** and **token secret** (generated per-account in the DocSpring dashboard).

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

The integration is **already built and submitted** as PR #21947 (6 actions + 1 instant webhook source). It's blocked on the base `docspring` app being registered on Pipedream's side with **custom-fields auth** — `token_id` + `token_secret`, combined as HTTP Basic auth — so an account can be connected and the PR reviewed/merged. Happy to adjust the auth field names/labels to whatever you register.

Note: DocSpring is region-aware (US / EU / self-hosted); the app file already handles API host selection per region.

**Are there specific actions or triggers you'd like to see for this app?**

All implemented in PR #21947:

Actions:
- Generate PDF
- Combine PDFs
- Create Data Request
- Create Signing Link
- Find Template
- Find Submission

Sources (triggers):
- New Event (Instant) — subscribes to a DocSpring v3 webhook (submission processed / failed / created / expired, data request completed / viewed, combined & batch processed / failed, template created / updated / deleted)

Source repo for the components: https://github.com/DocSpring/pipedream_integration

https://claude.ai/code/session_01NoNRaiRMMwfKsPBJu35XUE

Start by reviewing PR #21947 and the DocSpring integration source repo, then read the app registration requirements for custom-fields authentication. Verify that token_id and token_secret are registered for HTTP Basic auth and that the existing region-aware actions and webhook source are covered before requesting review.

Written by the indexing model from the issue text.