Notifications

00Overview

Create Oracle Cloud Notifications topics and manage the subscriptions attached to them — add email, SMS, HTTPS, Slack, PagerDuty or Oracle Function endpoints, resend a confirmation or confirm one, and unsubscribe or delete them. Publish a single message to a topic and it fans out to every confirmed subscriber, either as plain text or as per-protocol JSON. You can also list, fetch, update, and move topics and subscriptions between compartments, all from a flow.

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Notifications

1. In the node's Authentication dropdown, choose how to connect. Connect Oracle Cloud uses a managed Oracle Cloud connection — Flomation holds the signing key for you and is the recommended path — while API signing key (advanced) lets you supply your own key material directly.
2. For Connect Oracle Cloud, open your Flomation environment's credential settings and add an Oracle Cloud (API key) connection: give it a name, enter your Tenancy OCID and Region, and let Flomation generate a signing keypair for you.
3. Follow the guided deployment into Oracle Cloud, which provisions a dedicated user, group and policy scoped to the compartment you pick and uploads Flomation's public key. Complete the deployment, copy the new user's OCID back into the wizard, choose Connect, then Test connection (allow a short time — up to about 90 seconds — for the new key to activate).
4. Back in the node, leave Authentication on Connect Oracle Cloud and pick your connection in the Oracle Cloud connection field — the Tenancy, User, Region, Fingerprint and Compartment values are filled in for you.
5. To use API signing key (advanced) instead, in the Oracle Cloud Console open Profile → User settings → API keys, choose Add API key, download the private key, and copy the Configuration file preview Oracle shows — it lists your Tenancy OCID, User OCID, Key Fingerprint and Region.
6. Store the downloaded private-key PEM as a Flomation environment secret (e.g. notifications_secret) and select it in the node's Private Key (PEM) field, then fill in Tenancy OCID, User OCID, Region and Key Fingerprint (plus Private Key Passphrase if your key has one).

02Publish

OCI Notifications: Publish Message

oracle/notifications/publish_message · Action

Publish 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).

Returns: tool_result, message_id, timestamp, success, error

03Subscription

OCI Notifications: Move Subscription to Compartment

oracle/notifications/subscription_change_compartment · Action

Move a Notifications subscription to a different compartment. The endpoint, protocol and delivery state are unchanged — only the compartment scope moves.

Returns: tool_result, id, destination_compartment_id, success, error

OCI Notifications: Confirm Subscription

oracle/notifications/subscription_confirm · Action

Confirm 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.

Returns: tool_result, subscription_id, topic_id, endpoint, unsubscribe_url, message, success, error

OCI Notifications: Create Subscription

oracle/notifications/subscription_create · Action

Subscribe 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).

Returns: tool_result, subscription, id, lifecycle_state, success, error

OCI Notifications: Delete Subscription

oracle/notifications/subscription_delete · Action

Delete (unsubscribe) a Notifications subscription by its OCID. The endpoint stops receiving messages from the topic immediately — this cannot be undone.

Returns: tool_result, id, success, error

OCI Notifications: Get Subscription

oracle/notifications/subscription_get · Action

Fetch a single Notifications subscription by its OCID — its topic, protocol, endpoint and lifecycle state (PENDING until an email/HTTPS subscriber confirms, ACTIVE once delivering).

Returns: tool_result, subscription, id, lifecycle_state, success, error

OCI Notifications: List Subscriptions

oracle/notifications/subscription_list · Action

List the Oracle Cloud Notifications subscriptions in a compartment, optionally narrowed to a single topic. Walks pagination up to a safe cap.

Returns: tool_result, subscriptions, count, truncated, success, error

OCI Notifications: Resend Subscription Confirmation

oracle/notifications/subscription_resend_confirmation · Action

Resend the confirmation message for a Notifications subscription. Email and HTTPS subscriptions stay PENDING until the subscriber confirms — use this to re-send that confirmation.

Returns: tool_result, subscription, id, lifecycle_state, success, error

OCI Notifications: Unsubscribe

oracle/notifications/subscription_unsubscribe · Action

Unsubscribe 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.

Returns: tool_result, result, id, success, error

OCI Notifications: Update Subscription

oracle/notifications/subscription_update · Action

Update 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.

Returns: tool_result, id, success, error

04Topic

OCI Notifications: Move Topic to Compartment

oracle/notifications/topic_change_compartment · Action

Move an Oracle Cloud Notifications topic into a different compartment.

Returns: tool_result, topic_id, destination_compartment_id, success, error

OCI Notifications: Create Topic

oracle/notifications/topic_create · Action

Create an Oracle Cloud Notifications topic — the fan-out point that subscriptions attach to and messages are published to. Poll Get Topic until ACTIVE.

Returns: tool_result, topic, topic_id, lifecycle_state, success, error

OCI Notifications: Delete Topic

oracle/notifications/topic_delete · Action

Delete an Oracle Cloud Notifications topic by its OCID. This also removes its subscriptions and cannot be undone.

Returns: tool_result, topic_id, success, error

OCI Notifications: Get Topic

oracle/notifications/topic_get · Action

Fetch a single Oracle Cloud Notifications topic by its OCID.

Returns: tool_result, topic, topic_id, lifecycle_state, success, error

OCI Notifications: List Topics

oracle/notifications/topic_list · Action

List the Oracle Cloud Notifications topics in a compartment. Walks pagination up to a safe cap.

Returns: tool_result, topics, count, truncated, success, error

OCI Notifications: Update Topic

oracle/notifications/topic_update · Action

Update the description and free-form tags of an Oracle Cloud Notifications topic.

Returns: tool_result, topic, topic_id, lifecycle_state, success, error

05Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

• When Message Type is set to JSON, the body must be a JSON object containing an uppercase DEFAULT key, and that default value is delivered to any subscriber whose protocol has no matching per-protocol key of its own.
• Confirming a subscription requires the token from the confirmation link Oracle Cloud sends to the subscriber, so email and HTTPS subscriptions cannot be confirmed entirely from within a flow and remain pending and undeliverable until the subscriber acts.
• The list actions page through results up to a fixed ceiling of 25 pages, so a compartment holding a very large number of topics or subscriptions may not be returned in full by a single call.
• A freshly connected Oracle Cloud credential may need a short time for its new API key to become active, so actions run immediately after setup can fail with an authentication error until that propagation completes.