ORACLE CLOUD
Notifications actions
16 actions you can wire into a flow, alongside everything else in the Oracle Cloud integration.
Every Notifications action
- OCI Notifications: Confirm SubscriptionConfirm a pending Notifications subscription using the token from the confirmation link OCI sends the subscriber. Email and HTTPS subscriptions stay PENDING until confirmed: this completes the handshake so delivery can start.
- OCI Notifications: Create SubscriptionSubscribe an endpoint to a Notifications topic: email, SMS, an HTTPS URL, Slack, PagerDuty or an Oracle Function. For email and HTTPS the subscriber must confirm the subscription before delivery starts (it stays PENDING until then).
- OCI Notifications: Create TopicCreate an Oracle Cloud Notifications topic: the fan-out point that subscriptions attach to and messages are published to. Poll Get Topic until ACTIVE.
- OCI Notifications: Delete SubscriptionDelete (unsubscribe) a Notifications subscription by its OCID. The endpoint stops receiving messages from the topic immediately: this cannot be undone.
- OCI Notifications: Delete TopicDelete an Oracle Cloud Notifications topic by its OCID. This also removes its subscriptions and cannot be undone.
- OCI Notifications: Get SubscriptionFetch a single Notifications subscription by its OCID: its topic, protocol, endpoint and lifecycle state (PENDING until an email/HTTPS subscriber confirms, ACTIVE once delivering).
- OCI Notifications: Get TopicFetch a single Oracle Cloud Notifications topic by its OCID.
- OCI Notifications: List SubscriptionsList the Oracle Cloud Notifications subscriptions in a compartment, optionally narrowed to a single topic. Walks pagination up to a safe cap.
- OCI Notifications: List TopicsList the Oracle Cloud Notifications topics in a compartment. Walks pagination up to a safe cap.
- OCI Notifications: Move Subscription to CompartmentMove a Notifications subscription to a different compartment. The endpoint, protocol and delivery state are unchanged: only the compartment scope moves.
- OCI Notifications: Move Topic to CompartmentMove an Oracle Cloud Notifications topic into a different compartment.
- OCI Notifications: Publish MessagePublish a message to a Notifications topic: it fans out to every confirmed subscription (email, SMS, HTTPS, Slack and so on). The title becomes the email subject. Choose RAW_TEXT (the body verbatim) or JSON (per-protocol payloads).
- OCI Notifications: Resend Subscription ConfirmationResend the confirmation message for a Notifications subscription. Email and HTTPS subscriptions stay PENDING until the subscriber confirms: use this to re-send that confirmation.
- OCI Notifications: UnsubscribeUnsubscribe an endpoint from a Notifications topic using the subscription's OCID plus the token and protocol from the unsubscribe link OCI includes in every notification.
- OCI Notifications: Update SubscriptionUpdate a Notifications subscription: its delivery backoff-retry ceiling and/or freeform tags. A subscription's protocol and endpoint are fixed once created; recreate the subscription to change those.
- OCI Notifications: Update TopicUpdate the description and free-form tags of an Oracle Cloud Notifications topic.
Also in Oracle Cloud
API Gateway18 actionsAutonomous Database24 actionsBastion10 actionsBlock Volumes69 actionsCertificates20 actionsCloud Guard20 actionsCompute17 actionsContainer Engine44 actionsData Catalog26 actionsData Flow20 actionsDNS54 actionsDocument Understanding12 actionsEmail19 actionsEvents6 actionsExadata27 actionsFile Storage49 actionsFunctions15 actionsGenerative AI14 actionsIdentity90 actionsLanguage16 actionsLoad Balancer61 actionsLogging17 actionsMonitoring15 actionsMySQL HeatWave17 actionsNetwork Load Balancer33 actionsNetworking62 actionsNoSQL Database16 actionsObject Storage15 actionsQueue19 actionsSpeech13 actionsStreaming30 actionsVault50 actionsVision10 actionsVulnerability Scanning19 actionsWeb Application Acceleration13 actionsWeb Application Firewall17 actions
Put Notifications in a flow
These actions sit on the same canvas as every other integration, so a Notifications step can follow a form, a schedule or a message without any glue code.
