📖 Full Instructions 1. Remote Error Monitoring (The Sentinel)

Drag the TraceOps PRO Sentinel element onto your page (we recommend placing it inside a reusable header).

Go to your Workflows and add an event: A TraceOps PRO Sentinel - Error Caught.

Inside this workflow, add the action Send Webhook Alert.

Set the message to include dynamic data: "🚨 User [Current User's Email] experienced an error! Details: " + TraceOps PRO Sentinel's last_error_message.

Now, whenever a user's browser crashes in production, you get an instant Slack/Discord message!

2. Tracking Performance (The Timer)

To measure how long a process takes, add the Start Timer action at the beginning of your workflow. Give it a name (e.g., checkout_process).

At the end of your workflow (or when an API finishes), add the Stop Timer action using the same name.

The element will trigger the Timer Stopped event, and you can read the exact duration using the element's state: timer_result_ms.

3. Basic Debugging & Webhooks

Use Log to Console in any client-side workflow to print color-coded messages to your F12 developer console.

Use Send Webhook Alert anywhere in your backend or frontend workflows to securely push text alerts to a Slack or Discord webhook URL.


How to send Backend Logs to Datadog:

In your workflow, select the action Datadog Log Intake.

Paste your Datadog API Key and select your region site (e.g., datadoghq.com or datadoghq.eu).

Write your log message. You can optionally add service names (e.g., "stripe-webhook") and tags (e.g., "env:prod").

(Optional) Use the returned is_success state in the next step to confirm delivery.

How to send Backend Errors to Sentry:

In your workflow (usually inside an "Only when... error" condition), select the action Sentry Capture Event.

Paste your Sentry project DSN.

Pass the error message. You can also define the severity level (error, warning, info) and the environment.

How to Auto-Send Frontend Errors (Sentinel Auto-Pilot):

Place the TraceOps Sentinel element on your app's main pages or reusable header.

In the property editor, check auto_send_to_sentry to Yes and paste your Sentry DSN.

Check auto_send_to_webhook to Yes and paste your Discord/Slack webhook URL.

You are done! If a user's browser experiences a JavaScript crash or a failed API promise, the Sentinel will automatically catch it and send the alert to your tech stack in the background.


How to Master the TraceOps Security Suite:

1. Securing your Database with Hash Chaining

When a user performs a critical action (e.g., changing permissions), use the Create Immutable Audit Log action.

Crucial Step: In the previous_hash field, do a Search for Audit Logs: last item's Generated Hash. The plugin will link the new event to the old one cryptographically. Save the resulting generated_hash to your new Bubble database record.

2. Running a Security Audit (Tamper Detection)

Create a secure Admin Dashboard page. Add a button to run the Verify Tamper Detection action.

Pass your database lists (Hashes, Timestamps, States) into the action. Important: Ensure your Bubble Search is sorted by Creation Date (Oldest to Newest = Yes).

Check the is_tampered output. If it returns "yes", the tampered_index will tell you exactly which database row was maliciously altered.

3. Generating a Compliance Report

Run the Tamper Detection first.

Next, run Generate Compliance Export. Pass the is_tampered = no result into the is_verified field.

The action outputs a Base64 string. Use a File Downloader plugin or a Bubble link to let your admins download the official .json audit ledger!

4. Stopping Brute Force Attacks

Use the Detect Brute Force Activity action on your login or checkout pages.

Pass a list of recent failed attempt dates (Search for Failed Logins: each item's Creation Date).

Set your limits (e.g., 5 attempts in 60 seconds). If brute_force_detected is "yes", terminate the workflow and block the user!