Automated Informatica Agent Health Checks
Every night before the overnight window opens, WebRun signs into Informatica, checks each Secure Agent is running, tests the connections the scheduled taskflows depend on, confirms the schedules are enabled, logs readiness in Notion, and drafts an escalation email in Gmail for anything down.
How do I check Informatica agents and connections before the nightly batch?
Every night before the overnight window opens, WebRun signs into Informatica, checks each Secure Agent is running, tests every connection the scheduled taskflows depend on, and confirms the schedules are enabled. It logs readiness in Notion and drafts an escalation email in Gmail for anything down.
- Failures are caught before the batch window, not explained after it
- Every failing connection is tied to the taskflows it would block
- Intermittent failures show as a pattern across nights in Notion
Built for data engineers · ETL teams · data platform leads · BI operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
informatica.comin a real browser with your saved login - no setup, no API keys. -
1
Informatica - check agents and connections
informatica.com
WebRun opens Informatica to check agents and connections. - Sign in to Informatica and check every Secure Agent and runtime environment is up
- Run the test connection on each connection the night's scheduled taskflows depend on
- Confirm the job schedules for tonight are enabled and note anything disabled or paused
Done when Every agent, connection, and schedule in tonight's path has been checked.
-
2
Notion - log tonight's readiness
notion.so
WebRun opens Notion to log tonight's readiness. - Write tonight's readiness entry: agents up, connections passing, schedules enabled
- List every failure with the agent or connection name and the error shown
- Keep the entry alongside previous nights so a connection that fails intermittently becomes visible
Done when Tonight's readiness entry is in Notion with every failure named.
-
3
Gmail - draft the escalation email
gmail.com
WebRun opens Gmail to draft the escalation email. - Draft an escalation email to the on-call data engineer when anything fails its check
- Name the agent or connection, the error, and which taskflows depend on it tonight
- Leave the draft unsent and restart nothing. WebRun never restarts an agent or runs a job
Done when An escalation is drafted for every failure, ready for a person to send.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it restart an agent or trigger a job?
No. WebRun runs read checks and the built-in test connection only. It never restarts a Secure Agent, starts or stops a taskflow, or edits a schedule. Every fix is a human action.
Does it email the on-call engineer automatically?
No. The escalation is written as an unsent Gmail draft naming the failure and the taskflows it blocks. A person reads it and sends it.
How does it catch a flaky connection?
It keeps every night's result in Notion, so a connection that passes most nights and fails occasionally shows up as a pattern rather than a one-off.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.