Runliant guide

Start watching your first job in two steps

Keep your existing tools and accounts. Tell Runliant when the job should run and what a good result looks like, and it will watch for problems.

Start watching

1. Add the job directly

Enter its name, original tool, usual frequency, and allowed delay. Individuals do not need to create a client. Use optional job groups only when you manage several projects or separate clients. Result, duration, and cost checks can wait.

2. Put the receiving URL at the end of the original job

Choose the tool where the job runs. The dashboard then shows only the four steps for Make, Zapier, or that tool, with two copy buttons: Receiving address and Verification information. Paste those two values as shown. You do not need to enter a run ID, success status, or request body.

You do not have to decide whether setup worked: Save the step and run the real job once. The dashboard automatically changes from “Waiting to connect” to “Healthy” and shows “Connected.” If the job never finishes, Runliant alerts after its schedule and allowed delay. Some tools call the receiving address a “webhook.” The guide tells you what to click, what to copy, and what you will see when it works.

What Runliant checks

Check	When it alerts you	Example
Did not run	The planned time and allowed delay have passed	Hourly order update
Failed or got stuck	The job reports a failure or does not finish	Customer update stopped
Too few results	The job produced fewer results than expected	Daily leads returned zero
Unusual running time	The job finished too early or exceeded your time range	A step was skipped or a report slowed down
Cost too much	One run exceeded your spending limit	An intelligent task used too much
Ran twice	The same work ran more than once in a short time	An order may be fulfilled twice

Handle an alert

Each alert names the job group, job, and problem. Check the original tool first: if it also failed, fix the job; if it succeeded but Runliant received nothing or the wrong status, check the receiving URL, connection password, and final send step. Then claim the issue, add a note, and close it after recovery.

Account and data

Runliant does not need access to your other tool accounts. Share only what is needed to decide whether a job is healthy. Do not send passwords, card numbers, personal details, full order content, or files.

Common questions

Will healthy jobs keep bothering me?

No. Healthy runs are recorded quietly. You are alerted only when something needs attention.

Do I need to set every check at once?

No. Start by checking whether the job ran on time, then add more checks later.

What if I get stuck?

Open Help and contact and tell us which step stopped you. Do not send passwords or customer content.