Activity Logs

What are activity logs?#

Logs record every event that happens in your account: from receiving a lead via webhook to dispatching it to the CRM. They are the primary tool for monitoring lead flow and diagnosing issues.

When a lead doesn't appear on the platform or doesn't reach the CRM, logs are the first place you should check.

Accessing the logs#

In the sidebar menu, click on Logs. The page displays the most recent events in chronological order (newest first).

Event types#

Logs record four main types of events:

Type	Description	Example
Webhook received	A lead was received via webhook	"Lead received from API Key 'Form LP'"
Lead qualified	The lead went through the qualification pipeline	"Lead qualified with score 85"
Lead dispatched	The lead was sent to an integration	"Lead dispatched to HubSpot successfully"
Integration paused	An integration was temporarily paused	"HubSpot integration paused"
Integration resumed	A paused integration was reactivated	"HubSpot integration resumed"
Error	Something failed at some stage	"Error dispatching to Pipedrive: invalid API key"

Filtering the logs#

Use the filters at the top of the page to find specific events:

Filter by type

Select one or more event types: webhook received, qualification, dispatch, or error. Useful for viewing only failures, for example.

Filter by period

Set a date range to narrow down results. The default displays the last 7 days.

Filter by status

Filter between success, error, or pending to quickly identify pipeline issues.

Understanding common errors#

When something fails, the error log includes a descriptive message. Here are the most frequent errors:

Reception errors (webhook)#

Error	Cause	Solution
Invalid API Key	The key sent in the `x-api-key` header doesn't exist or has been deactivated	Check the API Key on the Receive Leads page
Invalid payload	The request body is not valid JSON	Confirm that Content-Type is `application/json` and the body is correctly formatted
Quota exceeded	The plan's lead limit has been reached	Upgrade your plan or wait for the next billing cycle

Qualification errors#

Error	Cause	Solution
Verification timeout	An external service (BrazilAPI, ProxyCheck) took too long to respond	The system retries automatically. If it persists, check the service status
Disposable email detected	The email uses a temporary email provider	Expected behavior -- the lead is flagged as disposable email

Dispatch errors#

Error	Cause	Solution
Expired token	The integration's OAuth token expired and couldn't be renewed	Disconnect and reconnect the integration
Rate limit	The destination CRM temporarily blocked due to excessive requests	The system waits and resends automatically
Required field missing	The destination CRM requires a field that wasn't sent	Review the integration's field mapping
Timeout	The destination CRM didn't respond in time	The system retries automatically. If it persists, check the CRM status

Zero Bad Leads automatically retries temporary errors (timeout, rate limit). Up to 5 attempts are made with increasing intervals. You can track each attempt in the logs.

Using logs for debugging#

When something doesn't work as expected, follow this flow:

Check reception

Filter by "Webhook received". If the lead doesn't appear here, the problem is with the webhook submission (API Key, payload format, or URL).

Check qualification

If the lead was received but not qualified, filter by qualification errors. Verify that the scoring profile is active.

Check dispatch

If the lead was qualified but didn't reach the CRM, filter by dispatch errors. Check the integration status and field mapping.

Logs are retained for 30 days. For older events, check the individual lead details, which maintain the complete history.