Before you begin
Use the account and records authorized for your task.
Ask the agency owner or the technical person responsible for the connection to coordinate the request. If the connection is only proposed, describe it as a scoping question rather than a failure of an installed integration.
Name the connection and operation
Give the external system name and the type of operation: a file import, an API request, or a webhook notification. State which system should supply the information and which should receive it. Describe the affected record type without including the candidate's personal details.
Describe the failure
Record the approximate time and timezone, expected result, actual result, and redacted error. State whether the problem affects one record or several, and when it last worked. Mention recent configuration changes if you know them.
Check for a partial result
Ask the authorized record owner to check whether the destination already contains the change. A failed request or interrupted screen can leave the result uncertain. Do not repeatedly resend a batch or write while duplicate creation is possible.
Prepare safe supporting context
Owners and managers can review API-key and webhook settings. Owners control changes. Share the non-secret configuration description and relevant error text; do not include API keys, signing secrets, passwords, authentication headers, or full request bodies containing personal data.
Send the request
Email hello@inferowl.com. Include the technical contact and the workflow impact, such as candidate import review being blocked. Use the approved secure process if support later requests additional records. This guide does not establish a response-time commitment or confirm support for an unscoped connector.
Describe one failed exchange
Choose a representative operation and identify the source, destination, record type, and expected change. Explain whether the issue concerns authentication, mapping, notification delivery, or the receiving record when you know. If the cause is unknown, report the observed behavior without assigning a technical explanation.
Ask the record owner to check for a partial result. A notification arriving does not prove the receiving update completed, and an interrupted response does not prove that nothing changed. State which parts were inspected before any retry.
Include the operational impact
Explain what work is blocked and whether an agreed manual process is available. Include the technical contact who can inspect the receiving system and confirm configuration changes. Keep credentials and full personal-data payloads out of the report. If the connection was never scoped or configured, describe the desired workflow as an implementation question so the team can establish the supported method and responsibilities before troubleshooting a presumed failure.
Was this guide helpful? Send feedback to the team.