Notifly

Notifly is notification infrastructure: workflows, subscribers, topics, and delivery across the email, SMS, push, chat and in-app channels you configure. The Notifly connector serves Claude two tools, search_tools and execute_typescript, through which it reaches eight operations - seven read-only and one write. Claude can list your workflows and open one to see its steps and channels, search subscribers and fetch one by id, list topics, and read the activity feed to check whether and how a notification was delivered. With your permission, it can also trigger a workflow so a real notification goes out. Sending is deliberately hard to do by accident. Connecting uses OAuth 2.1 with PKCE and a consent screen, and the scopes Claude receives come from your own account permissions. Three gates then stand in front of a real send: an organization-level dangerous-operations setting that is off by default and can only be turned on by a person signed in to Notifly; a two-step confirmation, where the first call returns a short-lived token bound to the exact organization, user, client, tool and arguments, so Claude must show you what will be sent before it can commit; and a live consent re-check at the moment the tool runs, so revoking a connected assistant stops the very next call rather than the next login. A caller-supplied transaction id makes retries idempotent. The read operations work as soon as you connect. Notifications go out through the channel providers your organization has already configured, to your own subscribers, from your own templates - nothing is sent to anyone you have not already onboarded. Review or revoke a connected assistant at any time from Connected AI apps in your Notifly settings. The connector processes no payments, generates no images, video or audio, and serves no ads. Documentation for connecting an assistant is at notifly.io/docs/connecting-ai-assistants.