Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.zentien.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Setting up Zentien involves five steps:
  1. Install the Salesforce package
  2. Connect your org to Zentien
  3. Configure unhandled error capture (email inbound)
  4. Add ErrorLogger.log() to your Apex code
  5. (Optional) Add Flow fault path monitoring and callout tracking

​
Step 1 — Install the Salesforce package

Open the link below while logged into your Salesforce org: Install Zentien → For sandbox orgs, use this link instead: Install Zentien (Sandbox) → When prompted, select Install for All Users and click Install. This installs the following components:
  • ErrorEvent__e — Platform Event for error data
  • ErrorLogger.cls — Apex class you call from try/catch blocks
  • CalloutEvent__e — Platform Event for outbound callout tracking
  • ZentienHttpCallout.cls — Drop-in wrapper for Http.send() to track callouts
  • Zentien Log Flow Error — Subflow to add to any Flow’s fault path
The package is an Unlocked Package — all source code is open and visible in your org. You can inspect every line.

​
Step 2 — Connect your org

  1. Log in to app.zentien.io
  2. Go to Orgs → Connect Org
  3. Select your environment (Production or Sandbox)
  4. You will be redirected to Salesforce — log in and click Allow
  5. You are redirected back to Zentien — your org is now connected
Zentien will immediately start listening for Platform Events from your org.

​
Step 3 — Configure unhandled error capture

Every org gets a unique inbound email address: {orgId}@zentienapp.com You can find your address on the Orgs page in the Zentien dashboard. Add this address in two places in your Salesforce org: Apex exceptions: Go to Setup → Apex Exception Email → External Email Addresses and add your Zentien inbound address. Flow faults: Go to Setup → Process Automation Settings and add your Zentien inbound address to the Send Process or Flow Error Email field. From now on, any unhandled Apex exception or Flow fault will automatically appear in your Zentien dashboard.
Salesforce may suppress repeated emails for the same exception within a short window. See FAQ for details.

​
Step 4 — Capture handled errors

Wrap your Apex code with ErrorLogger.log() to capture errors you catch explicitly: 
try {
    // your code here
} catch (Exception e) {
    ErrorLogger.log(e, 'YourClassName', 'yourMethodName');
}
Errors logged this way appear instantly in your Zentien dashboard via Platform Events — no email delay.

​
Step 5 — (Optional) Flow faults and callout tracking

​
Flow fault path monitoring

Add the Zentien Log Flow Error subflow to any Flow’s fault path to capture errors explicitly rather than relying on email. See Flow Fault Path Monitoring for step-by-step instructions.

​
Callout monitoring

Replace new Http().send(req) with ZentienHttpCallout.send(req) anywhere in your Apex code to track every outbound HTTP callout. See Callout Monitoring for details.

​
You’re done

Go to the Errors page in Zentien. Errors will start appearing as they occur in your org. Set up alerts to get notified via Slack or email when new errors are detected. Explore Salesforce Pulse to monitor org health, job runs, and governor limit trends.