400 – Bad Request

What it means:
Your configuration or payload is not properly structured. The destination platform (API or integration) is rejecting the request because the data being sent is missing required fields, formatted incorrectly, or not matching the expected schema.

How to fix it:

• Review the workflow payload (under “Recent Runs” or "History") and compare it to the API documentation of the connected app.

• Check for missing required fields, incorrect data types (e.g., sending text instead of a number), or malformed JSON.

• Validate field names in your destination mapping, make sure they match the exact naming used in the target system.

• If using custom code or transformations, ensure they produce a valid output before sending data to the next step.

401 – Unauthorized

What it means:
Datamorf tried to connect to a resource (like an API) but was not authorized. This typically occurs when authentication credentials are missing, expired, or invalid.

How to fix it:

• Reconnect the integration in the Integrations section to refresh your token or API key.

• Check that the API key, OAuth token, or credentials used are still valid and have the correct permissions.

• If using environment variables or headers, make sure they are properly configured and passed to the request.

• For APIs requiring user-specific tokens, verify that the correct user account is connected.

403 – Forbidden

What it means:
Datamorf successfully connected to the server, but your account or token does not have the necessary permissions to access the requested resource.

How to fix it:

• Verify your user role or API permissions in the external platform, some endpoints are restricted to admin or premium accounts.

• Ensure your API key or token has the correct scope (e.g., read/write access).

• If using an integration connected under a shared workspace, confirm that the workspace owner has granted proper access.

• Retry after updating access levels or reconnecting with an authorized account.

404 – Not Found

What it means:
The requested resource does not exist at the given URL or endpoint. This usually means the record ID or path you’re referencing is incorrect, or the resource has been deleted.

How to fix it:

• Double-check the endpoint URL or object ID being used.

• Confirm that the item exists in the source system (e.g., CRM, database, or API).

• Make sure your dynamic references (IDs or URLs generated in transformations) produce valid values.

• If the resource was recently created in another step, ensure there’s no timing issue, adding a small delay before the next step can help.

408 – Request Timeout

What it means:
The external service took too long to respond, and Datamorf terminated the connection to prevent the workflow from hanging indefinitely.

How to fix it:

• Retry the request, the issue may be temporary network latency.

• If this happens frequently, add a delay or retry configuration to your destination settings.

• Optimize payload size: avoid sending extremely large datasets in one request.

• Check the target service’s status or limits; it might be under maintenance or rate-limiting.

429 – Too Many Requests

What it means:
You’ve hit the rate limit of the external API. The target service temporarily blocked new requests to prevent overload.

How to fix it:

• Enable the retry mechanism in Datamorf’s destination configuration (available for paid plans).

• Add a delay between requests or reduce concurrency if you’re sending data in bulk.

• Check the API documentation for rate-limit rules and adapt your workflow schedule accordingly.

• If the error persists, contact the external service to request a higher rate limit.

206 – Partial Success

What it means:
The request was partially successful, some items or operations completed correctly, but others failed or returned warnings.

How to fix it:

• Open the workflow logs and review which items failed.

• Verify data consistency: some records might have missing or invalid fields.

• Check the API’s response message for more detailed error descriptions (Datamorf logs include them).

• If processing multiple records, ensure your batch handling or list iteration logic is correct.