Events

00Overview

Wire Oracle Cloud Events into your flows: create rules that watch for things happening in your tenancy — a resource being created, updated or deleted — and route each matched event to a Notifications topic, a stream or a function. List, fetch, update, enable or disable, move between compartments and delete those rules as automation runs, so a flow can manage the plumbing that turns cloud activity into downstream actions. Everything is scoped to one compartment and one region at a time.

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 Events

1. Choose how the node signs in with the Authentication dropdown: Connect Oracle Cloud uses a reusable managed connection (recommended), while API signing key (advanced) lets you supply raw signing-key credentials directly on the node.
2. For Connect Oracle Cloud, open your Flomation environment's credentials, add an Oracle Cloud connection and follow the wizard to authorise Flomation in your tenancy; a newly created signing key can take a short while to become active, so wait for the connection's test to succeed. Back in the node, leave Authentication on Connect Oracle Cloud and select this connection in Oracle Cloud connection.
3. For API signing key (advanced), sign in to the Oracle Cloud Console, open the Profile menu (the avatar, top-right) → My profile, then under Resources choose API keys → Add API key, let Oracle generate the pair and download the private key (a .pem file). Copy the values from the Configuration file preview into the node: tenancy → Tenancy OCID, user → User OCID, fingerprint → Key Fingerprint and region → Region (a plain key such as uk-london-1).
4. Set the Compartment OCID to the compartment whose Events rules you want to work with — find it under Identity & Security → Compartments, or use the tenancy OCID for the root compartment.
5. For the signing-key method, store the downloaded PEM as a Flomation environment secret (e.g. events_secret) and select it in the node's Private Key (PEM) field; if the key is passphrase-protected, add the passphrase as a secret too and pick it in Private Key Passphrase.

02Rule

OCI Events: Change Rule Compartment

oracle/events/rule_change_compartment · Action

Move an Events rule into a different compartment — the rule keeps its OCID, only its compartment placement changes.

Returns: tool_result, id, destination_compartment_id, success, error

OCI Events: Create Rule

oracle/events/rule_create · Action

Create an Events rule — a condition (a JSON event-matching filter) plus one action that routes matched events to a Notifications topic (ONS), a stream (OSS) or a function (FAAS).

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

OCI Events: Delete Rule

oracle/events/rule_delete · Action

Delete an Events rule by its OCID — it stops matching events and fanning them out.

Returns: tool_result, id, success, error

OCI Events: Get Rule

oracle/events/rule_get · Action

Fetch a single Events rule by its OCID — its condition, actions, enabled flag and lifecycle state.

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

OCI Events: List Rules

oracle/events/rule_list · Action

List the Oracle Cloud Events rules in a compartment, optionally filtered by display name and lifecycle state. Walks pagination up to a safe cap.

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

OCI Events: Update Rule

oracle/events/rule_update · Action

Partially update an Events rule — change only the display name, description, condition (JSON filter) or enabled flag you supply; blank fields are left unchanged and the rule's existing actions are preserved.

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

03Notes & Limitations

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

• Updating a rule never changes where its matched events go: the rule keeps its existing action and destination on every update, so to re-route matched events to a different topic, stream or function you must delete the rule and create a new one.
• Each rule you create carries exactly one action, so a single rule delivers matched events to one destination only; to reach several destinations, create a separate rule for each.
• Events is a per-region service, so a rule only matches activity raised in the region it connects to, and each region's rules are listed and managed independently; point the connection's region (or the Region field) at the region whose activity you want to capture.
• Listing rules returns up to 50 items per page and walks at most 25 pages, marking the result truncated when more rules remain, so narrow the display-name or lifecycle-state filter in compartments that hold very large numbers of rules.
• The condition is sent to Oracle Cloud exactly as you write it, so a malformed JSON filter or an event type that no service actually publishes shows up as a service error or a rule that silently never matches at run time, rather than being caught while you build the flow.