[APP] Scrupp

**Name of app / service**

Scrupp — https://scrupp.com

I work on Scrupp and would like to contribute the components myself once the app exists in the registry, per the [contribution guide](https://pipedream.com/docs/components/contributing/).

**Link to developer documentation**

- Docs: https://scrupp.com/docs
- Jobs API reference: https://scrupp.com/docs/api/integrations-jobs
- OpenAPI 3.1 spec: https://scrupp.com/api-docs/openapi-v1.yaml
- Postman collection: https://scrupp.com/api-docs/scrupp-api.postman_collection.json

Auth is a single API key sent as `Authorization: Bearer ` (an `X-API-Key` header and an `api_key` query parameter also work). A free `GET /api/v1/ping` exists specifically so a connection test costs nothing.

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

The workaround today is the generic HTTP request action, which works but leaves every user re-implementing the same async loop: extraction endpoints return a `job_id`, the caller polls `/jobs/{id}` until it reports `succeeded`, then reads `/jobs/{id}/result`. That is exactly the kind of thing a component should hide. A `callback_url` is also supported for workflows that would rather be told than poll.

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

Actions I would contribute, in order of usefulness:

1. **Find Decision Makers** — decision makers at a company from a domain, company name or company LinkedIn URL
2. **Enrich Company** — firmographics from a domain, name or LinkedIn URL
3. **Find Email** — work email from first name, last name and domain
4. **Verify Email** — deliverability check for a single address (synchronous, no job)
5. **Enrich LinkedIn Profile** — full profile from a profile URL, optionally with the email
6. **Export Search** — turn a Sales Navigator, LinkedIn or Apollo search URL into the people behind it

1–4 are single-record and map cleanly onto a step in a workflow. 6 returns many records and is the highest-value one for building a list.

Two API details that matter for component design: every create call accepts an `Idempotency-Key`, so a retried step returns the original job instead of starting a second billable one, and the poll response carries `retry_after` so a component can pace itself rather than guessing an interval. Rate limit is 2,000 requests/minute per key, with `X-RateLimit-*` headers on every response.

Start with the linked Pipedream component contribution guide, then read Scrupp's developer docs, OpenAPI spec, and Postman collection to map the proposed actions and authentication. Done means Scrupp is supported in the registry with the agreed actions and its asynchronous job behavior represented; the issue does not identify repository files or tests to run.

Written by the indexing model from the issue text.