How to Track Node-Level Logs, Enable Retries, and Use REST API Integrations in Pabbly Connect?

I have a few questions regarding workflow monitoring, logging, error handling, and API integrations in Pabbly Connect:

1. Node-level logs & deduplication:
   How can I track and store logs for each individual node/step in a workflow? I want to maintain important execution logs so I can identify duplicate executions and prevent deduplication issues.
   
   

2. Advanced logging:
   Is there any way to implement advanced/custom logging within a workflow to capture important details such as request data, response data, execution status, errors, and timestamps?
   
   

3. Single-node retry:
   How can I retry only a specific failed node/step instead of re-running the entire workflow? Is there a built-in option for single-node retry or error handling?
   
   

4. REST API / Advanced API integrations:
   Where can I find the REST API/Webhook/API Request node in Pabbly Connect? I want to connect APIs that are not available as native Pabbly integrations and need more advanced options for handling API requests, authentication, headers, parameters, and responses.

I would appreciate guidance on the recommended approach for implementing these features in Pabbly Connect, especially for production workflows where detailed logging, deduplication, and error handling are important.

Hello,

Thanks for reaching out. Here's guidance on each of your points for Pabbly Connect:

1. Node-level logs & deduplication:
Task history logs are automatically retained in your account for 15 days, after which they are purged. Bulk/direct downloading of historical logs or workflow data is not supported. For polling triggers, de-duplication is automatic — you don't need to reset it manually. If you want to keep detailed per-step logs beyond the 15-day window, the recommended approach is to log errors/data directly inside the workflow, for example via a Router fallback path that writes to Airtable or a database.

2. Advanced/custom logging:
There is no built-in advanced logging module, but you can implement custom logging inside a workflow by adding action steps that write request data, response data, execution status, errors, and timestamps to an external store (e.g., a database, Google Sheets, or Airtable). Note that failure email notifications are capped at one email per workflow per day, so parsing those emails will undercount repeat failures — logging inside the workflow gives you full fidelity.

3. Single-node retry:
You can re-execute failed steps without re-running everything. Go to History > Task History, click the specific Task History ID/row, then click Re-execute in the top-right corner. You'll get two options: 'Entire Workflow' (re-runs all steps) or 'Failed & Skipped Steps' (re-runs only the steps that failed or were skipped). Additionally, Auto Re-execution can be enabled in workflow settings so failed tasks retry automatically, and each action step has an 'Ignore Error' option to continue past a failed step.

4. REST API / Advanced API integrations:
For APIs that aren't available as native integrations, use the Custom API request (API by Pabbly) action, which supports custom headers, parameters, authentication (including Token/Bearer), and response handling. The response body becomes the step's output and is mappable downstream. Maximum payload size is 6 MB. For reference, see the API documentation at https://apidocs.pabbly.com/ and the integrations list at https://www.pabbly.com/connect/integrations/.

General best practices for production: use separate workflows per use case, add proper error handling, monitor Task History, and test in a staging environment before going live.