by Devino SolutionsCommunityRead your notification setup, send with confirmation
Notifly is notification infrastructure for workflows, subscribers, topics and delivery across the email, SMS, push, chat and in-app channels you configure. The Notifly connector gives AgentOne two tools, search_tools and execute_typescript, which reach eight operations: seven read-only and one write. AgentOne 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, AgentOne can also trigger a workflow so that a real notification goes out.
Sending is guarded against accidents. Connecting uses OAuth 2.1 with PKCE and a consent screen, and the scopes AgentOne receives come from your own account permissions. Three checks stand in front of a real send. First, an organization-level dangerous-operations setting is off by default and can only be turned on by a person signed in to Notifly. Second, a two-step confirmation applies: the first call returns a short-lived token bound to the exact organization, user, client, tool and arguments, so AgentOne must show you what will be sent before it can commit. Third, a live consent check runs when the tool executes, so revoking a connected assistant stops the next call immediately rather than at 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. You can 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.