Debut connects to NinjaOne, Hudu and Benji Pays. You find them in Settings, then Integrations. Integrations need the Practice plan or higher. Owners and admins connect, check and disconnect them.
What the status words mean
Connected. Everything works. The row says when it last synced.
Degraded. Debut is having trouble reaching the service. It tries again on its own.
Failed. The service refused Debut. You need to authorize it again or replace the key.
Disconnected. Someone disconnected it.
Choose Configure on a row to open the connection. The message at the top says what went wrong.
Checking a connection
Choose Check connection on the connection's page. Debut also checks NinjaOne and Hudu every hour, and every 15 minutes while a linked client is being onboarded. It asks Benji Pays about autopay still waiting every few minutes.
"Checked just now." The service answered.
"The check did not go through." The reason follows in the same line.
"A check is already running. Give it a minute, then look again."
Sync log on the Integrations page lists every check.
NinjaOne messages while connecting
"Check the region, the client id and the secret. Nothing was saved."
"NinjaOne has no API client with that client id in the region you chose." Pick the region you sign in to NinjaOne at, and check the client id.
"NinjaOne did not complete the authorization. Check the redirect URI on the API client matches exactly, then try again."
"The authorization was declined in NinjaOne. Nothing was saved."
"NinjaOne accepted the sign-in but refused to list organizations. Check the API client has the Monitoring and Management scopes, then connect again."
In NinjaOne, the API client needs application platform Web, the Monitoring and Management scopes, and the Authorization code and Refresh token grant types. The region is the host in your browser's address bar when you are signed in to NinjaOne.
NinjaOne messages after connecting
"NinjaOne refused Debut’s sign-in" followed by a short code. Choose Authorize again.
"NinjaOne refused the request (forbidden)." Tick the Monitoring and Management scopes on the API client, then authorize again.
"NinjaOne did not answer" or "NinjaOne answered with something unexpected". Debut tries again on the next pass.
Hudu messages while connecting
"Check the Hudu address (like acme.huducloud.com) and the API key. Nothing was saved."
"Hudu did not accept that key. Check it was copied whole, and that it does not only allow other addresses. Nothing was saved."
"Hudu accepted the key but will not list passwords with it. Make a new key with Password access turned on. Nothing was saved."
"Debut could not reach Hudu at that address. Check it is the address you use to sign in to Hudu. Nothing was saved."
Hudu messages after connecting
"Hudu refused Debut’s API key" followed by a short code. The key may have been deleted, may lack password access, or may not allow Debut's address. Choose Replace the API key.
"Hudu asked Debut to slow down (rate_limited). Debut tries again on the next pass."
"Hudu did not answer" or "Hudu answered with something unexpected". Debut tries again on the next pass.
Benji Pays messages while connecting
"Paste the whole API key and pick a currency. Nothing was saved."
"Benji Pays did not accept that key. Check it was copied whole. Nothing was saved."
"Benji Pays accepted the key but would not list customers with it. Make the key while signed in as a company admin. Nothing was saved."
The key lacks a permission Debut needs. It needs organizations:customers:read, organizations:payment-method-requests:create and organizations:payment-method-requests:read.
"Benji Pays has no accounting system connected, so it has no customers to link. Connect one in Benji Pays first. Nothing was saved."
"Debut could not reach Benji Pays. Try again in a moment. Nothing was saved."
Benji Pays messages after connecting
"Benji Pays refused Debut’s API key" followed by a short code. The key may have been deleted, may lack a permission, or the Benji Pays trial may have ended. Choose Replace the API key.
"Benji Pays did not answer" or "Benji Pays answered with something unexpected". Debut tries again on its own.
Benji Pays messages on a client
"Benji Pays would not make the autopay link. Check the customer in Benji Pays has an accounting id and a payment gateway for the currency."
"That Benji Pays customer is linked to another client. Unlink it there first."
"Benji Pays could not be reached just now. Nothing was changed. Try again in a moment."
"The autopay link is still being made. Try again in a moment."
Vault messages
"This workspace has no vault yet, so Debut has nowhere of yours to keep the key." Every workspace gets one at sign-up, so this should not happen. Contact BaselineZero support.
"The key could not be stored in your vault. Nothing was saved; try again in a moment."
"Debut could not read this connection’s key from your workspace’s vault. That is on our side; nothing is needed from you." If it does not clear, contact BaselineZero support.
Disconnecting never deletes what Debut wrote. When you are done with a connection, revoke the key or API client in the other service too.
Related guides
Page errors and "The connection dropped before the server answered"