When you ask Claude to take an action in TrustPager — update a contact, move an opportunity, change a field — and you get back a “No approval received” error, it means Claude never reached TrustPager. The call was blocked before it left Claude, and there is nothing wrong on the TrustPager side.
Why this happens
Claude shows an in-line approval prompt the first time it calls a write tool in a session. The prompt appears inside the Claude chat window, attached to the specific tool being called. If that prompt was missed, dismissed, or timed out before you responded, Claude treats it as rejected and the call never goes through.
This is a Claude safety behaviour, not a TrustPager API or permissions issue.
Why other writes may have worked fine
Approvals are per-tool, per-session. If you approved a different tool earlier in the same conversation — like creating a contact — that approval stays in place for the session. Only the tool that triggered a fresh prompt is blocked. So you can have a session where several actions work and one specific tool stops cold.
The fix
Retry the action in Claude. The approval prompt re-appears. Tap Allow to approve it once for this session, or Always allow to skip the prompt for that tool on this connector going forward.
You do not need to go anywhere in TrustPager to fix this. There is no approval queue, no API key issue, and no permissions change required at https://app.trustpager.com/settings/api.
If you haven’t connected TrustPager to Claude yet, see the setup guide at https://trustpager.com/help-center/connect-claude-to-trustpager.
