Neat Pulse — Troubleshooting

📘
Related setup guide
Setting up Neat Pulse? See the Neat Pulse connector setup guide.

Error message	Likely meaning (TL;DR)	Recommended next steps
Unable to authenticate against Neat.	Neat Pulse rejected the API key: it was deleted or regenerated, or the Organization ID does not match the key.	In Neat Pulse, open Settings → API Access and copy the current API key (generate one if none is shown). Confirm the Organization ID, paste both into the connector and save.
Missing read permissions, please make sure you assigned the read scope to the API key	The API key exists but was created without the read scope, so devices cannot be listed.	In Neat Pulse, edit the API key (or generate a new one) and give it the read scope. Then paste the key into the connector and save.

Error message

Likely meaning (TL;DR)

Recommended next steps

Unable to authenticate against Neat.

Neat Pulse rejected the API key: it was deleted or regenerated, or the Organization ID does not match the key.

In Neat Pulse, open Settings → API Access and copy the current API key (generate one if none is shown).

Confirm the Organization ID, paste both into the connector and save.

Missing read permissions, please make sure you assigned the read scope to the API key

The API key exists but was created without the read scope, so devices cannot be listed.

In Neat Pulse, edit the API key (or generate a new one) and give it the read scope.

Then paste the key into the connector and save.