Contact support
Send enough context to identify one source, request, or payment and reproduce the issue safely. Email info@cleanedweb.com for technical help, account questions, or source suitability.
On this page
Check the relevant workflow#
Review troubleshooting for request and data issues, billing for purchase questions, and source status for published source information.
If execution or payment has an uncertain outcome, inspect the existing run or purchase before retrying. A repeated action can create additional work or usage and make the original incident harder to isolate.
Prepare a technical report#
Include the following when available:
| Detail | Why it helps |
|---|---|
| Workspace and source identifier | Locates the affected integration and account boundary. |
| Definition version | Identifies the contract your application expected. |
| Run, request, or trace identifier | Connects the report to a particular execution. |
| Timestamp and timezone | Separates the incident from earlier or later attempts. |
| HTTP status and error text | Distinguishes validation, access, capacity, and execution errors. |
| Redacted inputs and selected limits | Shows the requested scope without exposing credentials. |
| Expected and actual result | Explains what would make the issue resolved. |
Attach a small redacted record example if a field is missing or incorrectly typed. Include the execution summary when reporting incomplete output. A screenshot can supplement the report, but identifiers and copied error text make it easier to investigate precisely.
You can use this template:
Workspace:
Source / definition version:
Run or trace identifier:
Observed at (with timezone):
Expected result:
Actual result / error:
Selected limits:
Reproduction steps:
Share run evidence safely#
Use Copy run link from the workspace when a recorded run is available. The link does not grant access, and a teammate still needs permission to its workspace. Opening the link reads the existing run instead of repeating it.
Do not include bearer tokens, session cookies, passwords, payment-card details, private signed URLs, or unnecessary personal information. Redact authorization headers and sensitive record fields before sharing logs or JSON.
For a suspected vulnerability or exposed credential, use the private reporting steps in secure your integration.
Billing and project questions#
For billing, include the purchase or invoice reference, charge date, amount, currency, and account email. Add the run identifier for disputed usage and follow the billing review policy.
For a new source or project, send a public collection URL, the records and fields you need, expected volume, collection frequency, and any deadline. Describe completeness or freshness requirements explicitly so the requested scope can be assessed.
For procurement, processing terms, or security review requirements, explain what your organization needs through contact before sending data subject to those requirements.