Coyote Sync connects your Coyote data to Divorcepath so child protection files can be created or updated without re-entering the same information in both systems. An admin creates the Divorcepath connection details, and your IT team runs a small PowerShell sync tool on a Windows computer or server that can access Coyote.
This article is for Divorcepath admins and IT teams. Examples use placeholder values. Do not copy placeholder keys or secrets into your real setup.
Who does what
| Step | Owner | Result |
|---|---|---|
| Create connection details in Divorcepath | Admin | Divorcepath shows the URL, key, and one-time secret needed by the sync tool. |
| Install the Windows sync tool | Your IT team | The Windows computer or server can read Coyote and connect to Divorcepath. |
| Run the discovery report | Your IT team, with Divorcepath support | Divorcepath can review expected files and counts before any matter data is sent. |
| Run and schedule the sync | Your IT team | Approved Coyote file updates are sent to Divorcepath on the agreed schedule. |
Before you start
- Admin access to your Divorcepath account.
- Coyote Sync available under your Divorcepath integrations.
- A Windows computer or server that can connect to Coyote.
- PowerShell 7 or later on that Windows computer or server.
- Read access to the Coyote data for files, parties, children, lawyers, and courts.
- The Coyote sync package from Divorcepath support.
1. Create connection details in Divorcepath
In Divorcepath, go to your organization integrations and open Coyote Sync. Click Create connection details.
Divorcepath will show three values for the setup file:
- Divorcepath URL
- Key
- Secret
The secret is shown only once. Use Copy settings right away if you want to copy the generated setup values into dpsync.config.json. Store the secret only on the Windows computer or server that runs the sync.
Files created through Coyote Sync will show the admin who created these connection details as the creator in Divorcepath.
2. Unzip the sync package
Place the package in a stable folder such as C:\dpsync. Keep the script, setup file, logs, exports, and state files together so Divorcepath support can review them if needed.
The package contains:
dpsync.ps1: the sync scriptdpsync.config.sample.json: the setup file templatedpsync-province-lookup.ps1: an optional helper that reports province lookup values only (no case records), if Divorcepath support asks for itREADME.md
As it runs, the script creates logs, out and state folders in the same location.
Copy dpsync.config.sample.json to dpsync.config.json. Do not send dpsync.config.json by email after the secret has been added.
3. Fill in dpsync.config.json
Open dpsync.config.json and add the Coyote database details plus the Divorcepath URL, key, and secret from the Coyote Sync page.
The setup file uses these field names:
apiUrlfor the Divorcepath URLapiKeyfor the keyapiSecretfor the secret
The table list should include the five Coyote tables or views used by Divorcepath:
DivorceMate_tblFilesDivorceMate_tblPartiesDivorceMate_tblChildrenDivorceMate_tblLawyersDivorceMate_tblCourts
Here is the sample setup file. Replace the server, database, key and secret with your own values:
{
"server": "SQLHOST\\INSTANCE",
"database": "CoyoteDM",
"auth": "integrated",
"tables": [
"DivorceMate_tblLawyers",
"DivorceMate_tblCourts",
"DivorceMate_tblFiles",
"DivorceMate_tblParties",
"DivorceMate_tblChildren"
],
"apiUrl": "https://www.divorcepath.com/webhooks/coyote",
"apiKey": "REPLACE_WITH_DIVORCEPATH_KEY",
"apiSecret": "REPLACE_WITH_DIVORCEPATH_SECRET",
"stateDir": ".\\state",
"outDir": ".\\out",
"batchSize": 200,
"requestTimeoutSeconds": 600
}
Leave auth as integrated to connect with the Windows account that runs the script.
4. Run the discovery report
Run discovery before any real sync. Discovery checks the Coyote connection, available data, columns, and row counts without sending matter data to Divorcepath.
pwsh -NoProfile -File .\dpsync.ps1 -Mode Discover
Discovery prints a log of what it found. Example output (abridged):
2026-10-10 09:14:02 [INFO] === dpsync-ps/0.1.4 starting (mode: Discover) ===
2026-10-10 09:14:02 [INFO] Loaded config from C:\dpsync\dpsync.config.json
2026-10-10 09:14:03 [INFO] Connected to SQLHOST\INSTANCE/CoyoteDM (auth: integrated)
2026-10-10 09:14:03 [INFO] Inspecting DivorceMate_tblFiles ...
2026-10-10 09:14:04 [INFO] Inspecting DivorceMate_tblParties ...
...
2026-10-10 09:14:07 [INFO] Discovery report written to:
2026-10-10 09:14:07 [INFO] .\out\dpsync-discovery-report.json
2026-10-10 09:14:07 [INFO] .\out\dpsync-discovery-report.txt
2026-10-10 09:14:07 [INFO] The report contains schema and row counts only - no case data.
2026-10-10 09:14:07 [INFO] === Done ===
Send both discovery reports to Divorcepath support:
out\dpsync-discovery-report.jsonout\dpsync-discovery-report.txt
5. Run the first real sync
After Divorcepath support reviews the discovery report, run the first full sync while Divorcepath support is available.
pwsh -NoProfile -File .\dpsync.ps1 -Mode Sync -Full
The sync log shows how many rows changed and each batch sent to Divorcepath. Example output (abridged):
2026-10-10 10:02:11 [INFO] === dpsync-ps/0.1.4 starting (mode: Sync) ===
2026-10-10 10:02:12 [INFO] -Full specified: ignoring saved state, all rows will be sent as upserts.
2026-10-10 10:02:15 [INFO] Detected 412 changed row(s).
2026-10-10 10:02:18 [INFO] Pushed batch 1/3 (200 changes) to https://www.divorcepath.com/webhooks/coyote in 2.6s
2026-10-10 10:02:21 [INFO] Pushed batch 2/3 (200 changes) to https://www.divorcepath.com/webhooks/coyote in 2.4s
2026-10-10 10:02:22 [INFO] Pushed batch 3/3 (12 changes) to https://www.divorcepath.com/webhooks/coyote in 0.9s
2026-10-10 10:02:22 [INFO] State saved to .\state\dpsync-state.json
2026-10-10 10:02:22 [INFO] === Done ===
Logs are kept in the logs folder, one file per day. If a batch fails, the state isn't updated and the changes are retried on the next run.
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 regular updates.
6. Schedule regular updates
Once the first sync has been reviewed, use Windows Task Scheduler to run regular updates at the agreed cadence. The scheduled task should use a dedicated Windows account with only the Coyote and network permissions needed for this sync.
Create a task with these settings:
| Setting | Value |
|---|---|
| Program/script | pwsh.exe |
| Add arguments | -NoProfile -File .\dpsync.ps1 -Mode Sync |
| Start in | C:\dpsync |
| Trigger | Repeat at the agreed interval, for example every 15 minutes |
| Security options | Run whether the user is logged on or not, using the dedicated sync account |
Scheduled runs use -Mode Sync without -Full, so only rows that changed since the last run are sent.
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 CFS details from Coyote are used for the applicant. |
| Parents or respondent parties | Parents are added as respondents and are not marked as your client. |
| Lawyer information | Lawyers are matched to lawyers already saved in Divorcepath when possible. If there is no match, Divorcepath creates a new lawyer contact. |
| Children and child lawyer information | Children are added to the file, including child lawyer information when supplied by Coyote. |
Troubleshooting
| Issue | What to check |
|---|---|
| Discovery row counts are zero | Confirm the Windows account can read the Coyote data and that the database name in dpsync.config.json is correct. |
| Sync is not authorized | Confirm the Divorcepath URL, key, and secret were copied exactly. If new connection details were created, update dpsync.config.json before the next sync. |
| Files do not appear after sync | Check the sync logs, then contact Divorcepath support with the sync time and account name. |
| Wrong lawyer or party assignment | Send the affected Coyote file ID and party names to Divorcepath support for mapping review. |
Security notes
- Use one setup file per Divorcepath account.
- Store the secret only on the Windows computer or server that runs the sync.
- Do not email the configured
dpsync.config.json. - Keep discovery reports and sync logs available during rollout.
- If you create new connection details in Divorcepath, update
dpsync.config.jsonbefore the next scheduled sync.