Coyote sync is a managed integration for organizations that use Coyote-Legal and want child protection files created or updated in Divorcepath from Coyote SQL data. The organization runs a small PowerShell agent on a Windows machine that can read the Coyote database. The agent sends signed batches to Divorcepath through the Coyote webhook.
This article is for organization administrators and IT teams. It uses sanitized screenshots and placeholder values; do not copy the placeholder credentials into production.
Who does what
| Step | Owner | Result |
|---|---|---|
| Enable Coyote Sync in Divorcepath | Organization admin or Divorcepath support | The integration appears under organization integrations. |
| Provision credentials | Divorcepath support | The organization receives an API URL, API key id, and secret through the approved secure channel. |
| Install and configure the agent | Organization IT | The Windows host can read Coyote SQL views and reach Divorcepath over HTTPS. |
| Validate discovery and first sync | Both teams | The first files are reviewed before the sync is scheduled. |
Before you start
- A Divorcepath organization that has Coyote Sync enabled.
- A Windows machine that can connect to the Coyote SQL database.
- PowerShell 7 or later on the Windows machine.
- Read access to the Coyote SQL views for files, parties, children, lawyers, and courts.
- The Coyote sync agent package from Divorcepath support.
- The organization-specific Divorcepath API URL, API key id, and API secret.
1. Unzip the agent package
Place the package in a stable folder such as C:\dpsync. Keep the script, configuration file, logs, exports, and state files together so support can review them if needed.
Copy dpsync.config.sample.json to dpsync.config.json. Do not send dpsync.config.json by email after secrets have been added.
2. Configure SQL and Divorcepath credentials
Open dpsync.config.json and update the SQL connection, Divorcepath endpoint, API key id, and API secret. The table list should include the five Coyote views used by Divorcepath:
DivorceMate_tblFilesDivorceMate_tblPartiesDivorceMate_tblChildrenDivorceMate_tblLawyersDivorceMate_tblCourts
3. Run discovery
Run discovery before any live sync. Discovery confirms SQL connectivity, the available views, columns, and row counts without posting matter data to Divorcepath.
pwsh -NoProfile -File .\dpsync.ps1 -Mode Discover
Send both discovery reports to Divorcepath support:
out\dpsync-discovery-report.jsonout\dpsync-discovery-report.txt
4. Run the first approved sync
After Divorcepath support confirms the discovery report, run the first full sync during an agreed support window.
pwsh -NoProfile -File .\dpsync.ps1 -Mode Sync -Full
After processing, review the first created or updated files in Divorcepath. Confirm the CFS applicant, parent respondents, lawyers, children, court location, and court file number before scheduling the agent.
5. Schedule incremental syncs
Once the first sync has been validated, use Windows Task Scheduler to run incremental syncs at the agreed cadence. The schedule should use a dedicated service account with only the SQL and network permissions required for this integration.
What Divorcepath creates
| Coyote data | Divorcepath result |
|---|---|
| File profile, court, and file number | A child protection file with court location and court file number. |
| CFS applicant information | The automated CAS applicant is replaced with the CFS details from Coyote. |
| Parents or respondent parties | Respondent parties are added and marked as not the organization's client. |
| Lawyer information | Lawyers are matched to organization professionals where possible; unmatched lawyers are created for future use. |
| Children and child lawyer information | Children are attached to the file, including child lawyer information when supplied. |
Troubleshooting
| Issue | What to check |
|---|---|
| Discovery row counts are zero | Confirm the SQL account can read the Coyote views and that the configured database is correct. |
| Sync returns unauthorized | Confirm the API key id and secret were copied exactly and that the endpoint URL is correct. |
| Files do not appear after sync | Check the agent logs, verify the webhook accepted the batches, and contact Divorcepath support with the sync time and organization name. |
| Wrong lawyer or party assignment | Send the affected Coyote source file id and party names to Divorcepath support for mapping review. |
Security notes
- Use one agent configuration per Divorcepath organization.
- Store API secrets only on the Windows host that runs the agent.
- Do not email the configured
dpsync.config.json. - Keep discovery and sync logs available during rollout.
- Contact Divorcepath support before rotating credentials or moving the agent to a new machine.
