Setup guides

Wire one success ping at the real end of the workflow.

These examples match the current MVP. Create a check first, choose an interval plus grace that matches normal runtime, then replace the placeholder URL below with your real success, fail, or start URL. Before the first success arrives, the overdue clock starts from the most recent create or update time.

Back to landing page

Zapier

  1. Choose an interval that matches how often the Zap should finish, then add grace for normal delays.
  2. Add a Webhooks by Zapier action at the true end of the successful path.
  3. Use the success URL: https://api.loopcheck.app/c/<your-token>/success
  4. Optional: wire the fail URL into a catch/error path: https://api.loopcheck.app/c/<your-token>/fail

Make

  1. Choose an interval that matches how often the scenario should finish, then add grace for normal delays.
  2. Add an HTTP Make a request module after the scenario really finishes.
  3. POST to the success URL: https://api.loopcheck.app/c/<your-token>/success
  4. Optional: send the start URL when a long-running run begins: https://api.loopcheck.app/c/<your-token>/start

n8n

  1. Choose an interval that matches how often the workflow should finish, then add grace for normal delays.
  2. Add an HTTP Request node at the end of the success path.
  3. POST to the success URL: https://api.loopcheck.app/c/<your-token>/success
  4. Optional: use the fail URL inside an error branch or error workflow: https://api.loopcheck.app/c/<your-token>/fail

Generic webhook / curl

  1. Choose an interval that matches how often the job should finish, then add grace for normal delays.
  2. Send a POST request from the final successful step of your script or workflow.
  3. Success URL: https://api.loopcheck.app/c/<your-token>/success
  4. Optional start URL for long-running work: https://api.loopcheck.app/c/<your-token>/start
curl -X POST 'https://api.loopcheck.app/c/<your-token>/success'