Monitoring Event Captures

Every time you trigger an event, Flowripple records it as a capture. Captures create an audit trail of all triggered events, making it easy to monitor activity, debug issues, and analyze patterns.

What are Captures?

A capture is a record of a single event trigger. Each capture contains:

Property	Description
`id`	Unique capture identifier
`createdAt`	Timestamp when the event was triggered
`payload`	The JSON data sent with the trigger
`processed`	Whether workflows have processed this capture
`processedAt`	Timestamp when processing completed

Event Triggered → Capture Created → Workflows Execute → Capture Marked Processed

Viewing Captures

Event Captures List

Navigate to the Events section in your dashboard
Click on an event to view its details
Select the Captures tab to see all triggers for that event

Each capture entry shows:

Capture ID and timestamp
Processing status (pending, processed, failed)
Quick preview of payload data

Capture Details

Click on any capture to view full details:

Complete payload: The entire JSON object sent with the trigger
Processing timeline: When the capture was received and processed
Workflow executions: Links to workflow runs triggered by this capture
Variable values: Extracted values available to workflows

Use capture details to debug workflow issues. You can see exactly what data was available when workflows executed.

Event Statistics

The event detail page displays statistics for triggered events:

Metrics Available

Metric	Description
Total Captures	All-time count of triggers for this event
Processed	Captures that completed workflow processing
Pending	Captures waiting for workflow execution
Failed	Captures where workflow processing failed

Time Series Charts

View trigger activity over time with interactive charts:

Daily triggers: Number of events per day
Processing times: How long workflows take to complete
Error rates: Percentage of failed processing

Date Range Selection

Filter statistics by time period:

Range	Description
Last 24 hours	Recent activity
Last 7 days	Weekly trends
Last 30 days	Monthly overview
Custom range	Select specific dates

Viewing Capture Payloads

Quick Preview

The captures list shows a truncated preview of each payload. Hover over the preview to see more detail.

Full Payload View

Click on a capture to open the full payload view:

{
  "orderId": "ord_789",
  "customer": {
    "id": "cust_123",
    "email": "[email protected]",
    "name": "Jane Smith"
  },
  "items": [
    { "sku": "PROD-001", "quantity": 2, "price": 29.99 },
    { "sku": "PROD-002", "quantity": 1, "price": 49.99 }
  ],
  "total": 109.97,
  "createdAt": "2024-01-15T14:30:00Z"
}

Payloads are displayed with syntax highlighting and can be copied to clipboard for debugging.

Debugging Workflow Failures

When workflows fail, use captures to identify the cause:

Common Issues

Missing payload fields

Check if the capture payload contains all expected fields. Missing data can cause workflow steps to fail.Solution: Ensure your trigger code sends consistent payloads with all required fields.

Invalid data types

Verify that payload values match expected types. A string where a number is expected can cause issues.Solution: Review the captured payload and compare against your event’s expected schema.

Empty or null values

Some workflow steps may fail on null or empty values.Solution: Provide default values when triggering events:

await flowripple.trigger('user.signup', {
  name: user.name || 'Unknown User',
  email: user.email // Required field
});

Payload too large

Very large payloads may cause processing issues.Solution: Send only necessary data. Avoid including large blobs or arrays.

Debugging Steps

Find the failed capture: Filter captures by status to find failures
Review the payload: Check if data is complete and correctly formatted
Check workflow execution: Click through to see which step failed
Compare with successful captures: Look at working captures to spot differences
Test with sample data: Manually trigger the event with corrected data

Best Practices

Monitor capture rates

Unusual spikes or drops in capture rates can indicate issues:

Sudden increase: Possible duplicate triggers or loops
Sudden decrease: Integration issues or code changes
Gradual decline: User engagement changes

Set up alerts

Configure alerts for:

High failure rates
No captures in expected time window
Processing delays

Use captures for testing

When debugging, trigger test events with known payloads and verify they appear as expected captures.

Review failed captures regularly

Schedule regular reviews of failed captures to catch issues before they affect users.

Getting Started

Events

HTTP Actions

Workflows

Monitoring Event Captures

Monitoring Event Captures

What are Captures?

Viewing Captures

Event Captures List

Capture Details

Event Statistics

Metrics Available

Time Series Charts

Date Range Selection

Viewing Capture Payloads

Quick Preview

Full Payload View

Debugging Workflow Failures

Common Issues

Debugging Steps

Best Practices

What’s Next?

Events Overview

Event Trigger

Getting Started

Events

HTTP Actions

Workflows

​Monitoring Event Captures

​What are Captures?

​Viewing Captures

​Event Captures List

​Capture Details

​Event Statistics

​Metrics Available

​Time Series Charts

​Date Range Selection

​Viewing Capture Payloads

​Quick Preview

​Full Payload View

​Debugging Workflow Failures

​Common Issues

​Debugging Steps

​Best Practices

​What’s Next?

Events Overview

Event Trigger

Monitoring Event Captures

What are Captures?

Viewing Captures

Event Captures List

Capture Details

Event Statistics

Metrics Available

Time Series Charts

Date Range Selection

Viewing Capture Payloads

Quick Preview

Full Payload View

Debugging Workflow Failures

Common Issues

Debugging Steps

Best Practices

What’s Next?