PipedreamHQ / PipedreamHQ/pipedream
[APP] Integration Recovery API
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Name of app / service**
Integration Recovery API
**Link to developer documentation**
https://integrationrecovery-api.com/docs
Public integration source and examples:
https://github.com/API-Disk-Integrations/integration-recovery
**Is lack of support preventing you from moving forward, or do you have a workaround?**
Yes. The API can be called through a generic HTTP step, but the missing registered app blocks a discoverable, reviewed Registry action with managed secret authentication. A provider-free action candidate and deterministic fixtures are ready locally; no component PR will be opened until Pipedream creates the app directory.
**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!**
Initial action: **Get Repair Plan / Check Integration Drift**. It sends one caller-supplied previous/current integration snapshot pair (or a bounded ordered batch) to `POST /v1/checks` and returns the ordered drift diagnosis and repair plan without applying remediation or retrying automatically.
No trigger is requested in the first release. A trigger would be proposed only after genuine event/list semantics and customer demand are evidenced.
Contributor guide
Research direction
Start by reviewing the Integration Recovery API developer documentation and its public integration source, then inspect the repository's app-registration process for the required app directory and managed secret setup. Done means the Integration Recovery API is registered with a reviewed action for POST /v1/checks, deterministic fixtures cover the ordered drift diagnosis and repair-plan response, and no trigger or automatic remediation is added.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100