Quick taskAutomation
Find the missing handoff.
Ask your AI to inspect database activity and scoped webhook delivery history so your team can understand a failed automation.
A complete worked example
Find where a lead handoff stopped.
A lead is present in Fermium, but the follow-up team cannot find it in the next tool. The agent has access to this project's delivery history.
Fictional project and sample data. This preview does not submit, publish, or change access.
Connection operators · illustrative result
The form saved. Delivery failed.
A diagnostic summary using identifiers and delivery status rather than private response contents.
- Collection
- R17 saved successfully
- Delivery
- E42 · receiver returned HTTP 401
- Next check
- Confirm the receiver's authentication configuration
What this establishes
The submission exists, but the receiver rejected this attempt. Inspect the connection and receiver configuration before retrying. This summary does not reveal a signing secret or claim that the receiver processed the event.
What the recipient can access
Event identifiers, delivery outcome, and the next investigation step.
Kept out of this handoff
Submitted answers, credentials, and unrelated delivery logs.
How it runs
- Locate the responseFind the form event in database activity using its record ID and approximate time.
- Follow the deliveryInspect the scoped connection and its delivery attempts to see whether the receiver accepted the event.
- Choose the next actionCheck the external workflow's run history when delivery succeeded, or review connection settings when delivery failed.
- You getAn evidence-based explanation of the event, its delivery attempts, and the next place to investigate.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Inspect this project's database activity and webhook deliveries. Find the event for [record or time] and explain whether the response was saved, queued, attempted, and accepted by the receiver. Use event IDs and delivery status as evidence. Keep answer contents and secrets out of the diagnostic summary. If delivery succeeded, identify what I should check in n8n or Zapier. Suggest the next action and wait for my instruction before changing a connection or sending a test.
What this workflow needs
Fermium can show its own activity and delivery results. Diagnosing the receiver's internal execution requires access to that service's logs.
Can an agent inspect another team's private database logs?
Database activity and scoped delivery tools check the current user's permissions. The agent receives access through its authorized Fermium connection.