Skip to main content
Actions do the work in a workflow, using data from the trigger and from earlier steps. Most actions also have Optional Filters, which skip the action when they don’t match.

Ticket actions

Creates a new ticket, fully configured in a single step. Use trigger data to fill in the details.Input fields:
  • Workspace and Channel - Where the ticket is created
  • Title, Description, Status, Priority, and Type
  • Requester and Author - Who the ticket is for, and who it is recorded as coming from
  • Assignee, Followers, Tags, Category, and Due date
  • Approvers - Set on the ticket at creation, so the approval is in place before anyone opens it
  • Parent ticket - Links the new ticket as a child at creation time. The parent does not have to be in the same workspace as the child.
  • Form - The form to attach, and its field values
  • Ticket attributes - Values for the workspace’s custom fields
Because every relationship is set on the create, you rarely need a follow-up Update Ticket step.Cross-workspace creation: Select any channel you have access to, including channels in other workspaces. If the destination channel is in a different workspace, Ravenna treats this as a cross-workspace create and publishes the ticket immediately. Triggers, notifications, and workflows in the destination workspace fire as if the ticket were created normally. Same-workspace creates skip that dispatch so the workflow does not retrigger itself.Copying form data onto the new ticket: Set the Form input to a reference to another ticket’s form, such as the trigger ticket’s, and the new ticket carries that ticket’s field values. Anything you set explicitly on the step overrides the copied value. This is how a handoff carries its data, so the receiving team’s workflow can branch on the original submission instead of reading back from the source ticket.
The Ticket attributes pickers list the attributes of the workflow’s own workspace, not the destination’s. On a cross-workspace create, pass destination-specific values through the copied form or the description instead. Update Ticket has no workspace field, so set everything the destination needs on the create.
Output data:
  • ticketId - The ID of the created ticket
  • isSuccess - Boolean indicating whether creation succeeded
Common use cases:
  • Create follow-up tickets for multi-step processes
  • Generate tickets from Slack messages or external events
  • Hand off work to another team’s workspace and let their automations pick it up
  • Fan one intake event out to a child ticket per team, all linked to a shared parent
Changes properties on an existing ticket, such as priority, tags, status, assignee, requester, parent ticket, or custom fields.Common use cases:
  • Escalate tickets by changing priority
  • Update custom fields based on workflow logic
  • Set a parent ticket to organize tickets into a hierarchy
  • Reassign the requester when a ticket is submitted on behalf of someone else
Publishes a newly created ticket, making it visible and sending its notifications. Use it when you configure a ticket across several steps before anyone should see it.Common use cases:
  • Create and configure a ticket across multiple steps before making it visible
  • Control when notifications are sent for new tickets
Moves a ticket to the status you choose.Common use cases:
  • Auto-resolve tickets meeting specific criteria
  • Move tickets through workflow stages
Changes a ticket’s priority.Common use cases:
  • Escalate urgent issues automatically
  • Adjust priorities based on SLA requirements
Changes a ticket’s type: Service, Incident, Problem, Change, or Access.Output data:
  • type - The type the ticket was set to
Common use cases:
  • Reclassify a request as an incident when a Custom Prompt or AI Decision Maker flags an outage
  • Set the type from a form answer
Assigns one person to the ticket.Strategy:
  • User - Assigns the user you choose.
  • Round Robin - Picks one person from a list of users or groups in rotation, to balance workload. Groups are expanded into their members when the workflow runs.
  • Random - Picks one person from the list at random.
Skip unavailable assignees: For Round Robin and Random, turn on Skip Unavailable Assignees to pass over users who are out of office or outside the working hours set in their business schedule. It is off by default. A skipped user keeps their place in the rotation and is picked again once they are available. If nobody in the list is available, the step assigns someone anyway so the ticket always gets an owner.Rotation scope: Each Add Assignee step keeps its own rotation. Two Round Robin steps that share the same list rotate independently rather than continuing one shared rotation, so you can stage hand-offs (for example, a triage assignee and a later reviewer) without one step skipping members of the other.Common use cases:
  • Distribute tickets across a group with Round Robin for load balancing
  • Route tickets to a specific owner based on form or channel
  • Stage multiple Round Robin assignments (triage, then review) in one workflow
Adds followers to a ticket to keep stakeholders informed. Select Ravenna members or groups, including groups synced from integrations.Common use cases:
  • Add managers to high-priority tickets
  • Include cross-functional stakeholders
Adds tags to a ticket for categorization and filtering.Common use cases:
  • Auto-tag based on content analysis
  • Categorize by form type
  • Add processing status tags
Moves a ticket to another channel, optionally in another workspace and to a specific status. The ticket keeps its history.Common use cases:
  • Transfer tickets between teams
  • Escalate to a different department’s workspace
Shares a ticket to a channel in another workspace. Unlike Move Ticket, the original ticket stays in its current channel and the destination gains access to the same ticket. Select a workspace first, then a channel within it. See sharing tickets.Common use cases:
  • Give another team visibility into a ticket without transferring ownership
  • Share requests across departments for collaborative resolution
Posts a message on a ticket.Configuration:
  • Message Type: Who sees the message. Defaults to Public.
    • Public: Everyone on the ticket sees the message.
    • Private: Only your team sees the message, as a private note.
    • DM: Ravenna sends the message to one person about the ticket.
  • Recipient: The user who receives the DM. Required when Message Type is DM.
A DM reaches the recipient in every app they are connected to: a direct message from the Ravenna app in Slack, a personal chat in Microsoft Teams, and email. On the ticket timeline, team members see the DM as its own card that names the recipient and the apps it was sent through. A failed delivery shows as a red label with the error on hover.Common use cases:
  • Send automated updates to requesters
  • Request additional information
  • Message an approver, manager, or new hire directly about a ticket
Imports a task template into a ticket, attaching its tasks, assignees, and ordering.Common use cases:
  • Attach onboarding checklists to new hire tickets
  • Apply standard operating procedures to incident tickets
Marks tasks on the ticket as complete. Every filter is optional, and a task must match all the ones you set:Output data:
  • completedTaskItemIds (Completed Tasks) - The tasks that were marked complete
Common use cases:
  • Check off a checklist item after an approval is granted
  • Close out remaining tasks when a ticket is resolved
Finds tickets matching a filter. Add at least one filter.Configuration:
  • Ticket Filter: One or more filter groups on ticket properties. Groups combine with OR, and conditions inside a group combine with AND.
  • Limit: Maximum number of tickets to return (1 to 50, default 50).
Output data:
  • ticketIds (Ticket search results) - Array of matching ticket IDs
Common use cases:
  • Find related or duplicate tickets
  • Check for existing tickets before creating new ones
  • Pair with a Cron trigger and a Loop for scheduled clean-ups
Finds users in your organization matching a filter. Returns user IDs that later steps can use, for example to assign, notify, or iterate over with a Loop.Configuration:
  • User Filter: One or more filter groups on user attributes such as name, email, or group membership. Groups combine with OR, and conditions inside a group combine with AND.
  • Limit: Maximum number of users to return. Set a value from 1 to 10, or leave it empty to return up to 50.
Output data:
  • userIds - Array of user IDs matching the filter
Common use cases:
  • Look up the members of a group or team to notify or assign
  • Build a dynamic recipient list for Add Assignee, Add Followers, or Send Email
  • Combine with Loop to run actions per matching user
Starts a lifecycle from a published template. Set the Template, the Person (or Person’s email, to find them from an address), the Anchor date and who it’s Started by, a member of the workspace. Manager defaults to the person’s manager in your HR system, then to Other stakeholders, one person who fills the template’s other roles.Output data: the Lifecycle ID and Lifecycle ticket.Common use cases:
  • Start onboarding when the Employee Hired trigger fires
  • Start a lifecycle from a webhook sent by another system
Learn more about lifecycles

Approval actions

Pair an approval action with Wait for Approval to pause the workflow until a decision is made.
Adds an to the ticket with the approvers and policy you choose. If the ticket already has approval rounds, its approval goes back to in progress, so a Wait for Approval after this step waits for the new round.Input fields:
  • Approvers (required) - Users or groups who can approve
  • Approval Policy - Any can approve (default), All must approve, or Majority must approve
  • Assignment Strategy:
    • All (default) - Every selected approver is added to the round.
    • Round Robin - One approver is picked from the list in rotation.
    • Auto Approve - The ticket is approved immediately by the workspace bot. If the ticket already has an approval round in progress, the step adds every listed user instead, as if you had chosen All.
Output data:
  • approverIds (Approvers) - The approvers added to the round
Common use cases:
  • Require a manager’s approval, then a second team’s approval, by adding one round after another
  • Auto-approve low-risk requests on one branch and require approval on another
Applies an approval template to the ticket. The template’s rounds replace any approval rounds already on the ticket, and the approval starts.Output data:
  • ticketId - The ticket the template was applied to
  • approvalTemplateId - The template that was applied
The workflow continues to the next step as soon as the rounds are created. To hold it until approvers decide, add Wait for Approval after this step.Common use cases:
  • Apply the same multi-round approval process to every request of a given type
  • Pick a template per department with If / Else
The older way to add approvers. Prefer Add Approval Round, which also sets the approval policy. Add Approvers creates an approval round from the users or groups you select, with an All or Round Robin strategy.
Learn more about approvals in workflows

Wait actions

Wait actions pause the run. While a run is paused, it shows as waiting in the run log.
Duration fields take a number and a unit: m (minutes), h (hours), d (days), w (weeks), or y (years), such as 30m, 8h, or 2d. Where a step allows it, type Forever to wait with no time limit.
Pauses for a set duration before the next step runs.Configuration:
  • Duration - How long to wait. Defaults to 8h. Accepts Forever, and relative durations like 1d - 8h.
  • From Date (optional) - The date to count from. Defaults to the time the step runs.
  • Timezone (optional) - The timezone used for the calculation.
Common use cases:
  • Add a delay between actions
  • Create timed follow-ups
Pauses until a specific date and time, optionally offset from it. Use this to schedule actions around key dates like onboarding, license renewals, or contract deadlines.Configuration:
  • Target Date - A fixed date or a dynamic value, such as a date field from a form.
  • Time - The time of day to continue on the target date.
  • Timezone - The timezone for that time.
  • Date Offset (optional) - Moves the target earlier or later. A positive offset such as 5d waits until after the date. A negative offset such as -5d waits until before it, so -5d on an onboarding date of March 20 continues on March 15.
Common use cases:
  • Send reminders before a deadline or renewal date
  • Start onboarding tasks relative to a start date
  • Revoke temporary access on its end date
Pauses until the ticket’s are decided or the timeout passes. The step branches into On Declined, On Approved, and On Timeout.Configuration:
  • Duration - Maximum time to wait. Defaults to 3d. If it passes without a decision, the workflow continues down On Timeout.
Output data:
  • isApproved - Boolean indicating whether the ticket was approved
  • isTimedOut - Boolean indicating whether the wait expired before a decision
  • approvedByUserIds (Approved By) - Array of user IDs who approved the ticket, across all of its approval rounds
  • declinedByUserIds (Declined By) - Array of user IDs who declined the ticket, across all of its approval rounds
  • Force Approved By - The user who force-approved the ticket, if anyone did
The approver’s decline reason is posted on the ticket automatically. See decline reasons.Branches:
  • On Approved runs when the ticket is approved.
  • On Declined runs on an explicit decline only.
  • On Timeout runs when the duration passes before anyone decides. Use it to escalate, notify the requester, or close the ticket.
Common use cases:
  • Gate access provisioning until approved
  • Notify the requester when a request is declined
  • Escalate stalled approvals
Pauses until one of the chosen people sends a message on the ticket. Workflow-generated and AI-generated messages never count.Configuration:
  • Message Authors (required) - Users or groups whose messages resume the workflow
  • Duration - Maximum wait time. Defaults to 3d.
  • Message Sources (optional) - Web, Email, or Slack. Leave empty to accept every source.
Output data:
  • isSuccess - Boolean indicating whether a matching message arrived before the timeout
  • ticketMessageId - The message that resumed the workflow, when one arrived
Common use cases:
  • Wait for a requester’s reply before continuing
  • Pause until a specific team member provides input
Pauses until the ticket has gone without new messages for a set duration, then continues.Configuration:
  • Duration - How long the ticket must stay quiet. Defaults to 8h.
  • Users (optional) - Only count messages from these users. Leave empty to count messages from anyone.
Common use cases:
  • Auto-resolve tickets after a quiet period
  • Send a reminder before auto-closing
Watches the ticket until its conditions match, then continues. Each time the ticket is updated, Ravenna checks the step’s conditions again. If they still don’t match when the duration passes, the path stops there.Configuration:
  • Duration - How long to keep watching. Defaults to 8h.
  • Optional Filters - The ticket state to wait for. Unlike other actions, these conditions don’t skip the step; the step waits until they match.
Output data:
  • isSuccess - true once the conditions match
Common use cases:
  • Wait for a ticket to reach a status before continuing
  • Continue only after an assignee or field is set
A Slack action that watches the Ravenna agent’s Slack conversation, usually after an AI Start Conversation Trigger. The run continues once the agent has had no activity in the thread for the duration. If someone leaves feedback on the agent’s reply first, the path stops.Configuration:
  • Duration - How long the thread must be quiet. Defaults to 24h.
Common use cases:
  • Follow up with the requester after the agent’s conversation goes quiet
Learn more about waits, loops, and Goto

Control flow actions

Checks conditions and records whether they matched, without ever stopping the workflow. Steps after it read the result and decide what to do, usually in their Optional Filters.Output data:
  • Conditional > Is Success - Boolean indicating whether the conditions matched
Common use cases:
  • Run one action if any of several checks match, with one Conditional per check feeding that action
  • Save a check’s result for a step further down the workflow
Checks conditions and splits the workflow into a True path and a False path. Only the path that matches runs, so If / Else acts as a gate.A step that several True or False paths lead into runs only if every one of them passes. To run one action when any of several checks match, use Conditionals instead.Output data:
  • Is Success - Boolean indicating whether the conditions matched
Common use cases:
  • Do different things depending on ticket properties, such as priority or form answers
  • Stop a path entirely when a check fails
Jumps back to an earlier step in the same path and runs it again. Goto can only jump upstream, to a step that runs before it.Configuration:
  • Step - The earlier step to jump to.
  • Budget - How many times the jump can happen in one run. Defaults to 1, maximum 100. Once the budget is used up, the workflow continues down On Limit Reached instead of jumping.
Common use cases:
  • Retry a check after a wait, such as polling an external system until it is ready
  • Re-send a reminder a fixed number of times
Runs the steps inside the loop once for each item in a list. A loop processes at most 50 items; set a lower Limit to process fewer.Loopable collections:
  • Array outputs from earlier steps, such as ticketIds from Search Tickets or userIds from Search Users.
  • Multi-value custom fields on the ticket’s form, including Multi-Select, User Multi-Select, Multi-Application Select, and Tag Select fields. Reference the field like any other form value and pick it as the loop’s collection.
Inside the loop, each iteration exposes a typed item. For entity multi-selects the item is the underlying ID (for example, a user, application, or tag ID), which actions like Add Assignee, Add Followers, or Update Ticket accept directly. For a generic Multi-Select the item is the selected option as text.Common use cases:
  • Process each result of a search
  • Send notifications to a list of users
  • Act on each member, application, or tag a requester selected on the intake form

AI actions

Generates a short summary of a ticket’s conversation: what happened, what was decided, and the outcome.Common use cases:
  • Generate ticket summaries for handoffs
  • Summarize resolution steps
Makes a judgment call that needs context rather than a field check, then continues down a True or False path, like If / Else.Common use cases:
  • Route tickets based on content analysis
  • Evaluate sentiment for escalation
Runs AI reasoning with your instructions to analyze context, generate responses, or make decisions within the workflow.Inputs:
  • Prompt - Instructions for the AI. Insert dynamic values from earlier steps to pass in data.
  • Ticket (optional) - A ticket to include as context, such as the trigger ticket.
With a ticket, the AI reasons over its details alongside your prompt: the title, description, request type, links, created and updated timestamps, custom field values, and the ticket activity log. Use this when your prompt asks about the ticket itself, such as “Summarize what the requester still needs” or “Classify the urgency of this request.”Output:
  • AI Response - The AI’s answer, available to later steps.
  • Outputs - Structured values Ravenna infers from your prompt, such as a category or a yes/no decision, so later steps can reference each one directly.
Common use cases:
  • Draft response messages based on ticket content
  • Extract structured data from unstructured text
  • Analyze sentiment or urgency from messages

Messaging actions

Sends an email to the people you choose. Find it under the Tool group in the action picker. Configure recipients, subject, and body with dynamic values from the workflow.Body formatting:The body field is a rich text editor. Use the toolbar to add bold, italic, lists, links, and headings. Type formatted text directly in the editor instead of pasting raw HTML or Markdown.Recipients added as followers:When this action sends an email from a ticket, Ravenna adds the recipients as followers on that ticket, so they stay in the loop on later replies. Resolved Ravenna users and To and CC addresses that map to users in your organization are included. BCC recipients are never added.
  • Existing followers, approvers, the requester, assignee, and author are skipped.
  • Email addresses that don’t match a Ravenna user are ignored.
  • Followers are not added when the ticket is private.
  • If adding followers fails, the email is still sent and the error is logged.
Inputs:Sender address behavior:
  • When a verified email domain exists and Sender Address is set, Ravenna sends from <localPart>@<verified-domain>. The action does not offer a domain picker.
  • When Sender Address is blank, Ravenna uses the organization-level sender address from Organization Settings > Email, if one is configured.
  • When the workflow runs on a ticket, Ravenna sets Reply-To to the ticket’s address (ticket+<id>@…) so replies thread back to the same ticket.
  • When no verified email domain exists, Ravenna sends from the default support sender (support@<ravenna-inbound-domain>) for sends without a ticket, or from the ticket’s address when running on a ticket.
Common use cases:
  • Notify external stakeholders who are not in Slack
  • Send formal communications like approval confirmations or access grants
  • Deliver summary reports or status updates by email
Sends a Ravenna form to a user for an existing ticket. The step finishes as soon as the request is sent, without waiting for the submission. When the user submits, the values are written to the ticket and a confirmation message is sent.Inputs:Prefilling and locking fields:Pre-fill any field when you configure the action, so the recipient sees the values already filled in. Each pre-filled field has a lock toggle:
  • Unlocked (default): the value is a starting point and the recipient can change it.
  • Locked: the field is read-only for the recipient. Fields you did not pre-fill stay editable.
Locks are enforced when the form is submitted, from Slack, email, or the portal. A submission that changes a locked field is rejected with FORM_LOCKED_FIELD_CHANGED. You can only lock fields you also pre-fill.Email delivery:With Email, Ravenna emails the recipient a link to the pre-filled form. A form request bypasses the recipient’s “messages” notification preference, so it arrives even if they’ve muted general ticket messages. If the ticket is not private, the recipient is also added as a follower.Common use cases:
  • Collect required details before continuing
  • Send a targeted form to an approver or hiring manager over email
  • Pre-fill known fields and lock them, while asking the recipient for the rest
Sends a customer satisfaction survey to a user, usually after the ticket is resolved.Common use cases:
  • Survey after ticket resolution
  • Measure service quality

Access actions

Find these actions under the Access group in the action picker.
Searches the entitlements in your organization and returns the matching entitlement IDs plus the users who hold them.Configuration:
  • Entitlement Filter: One or more filter groups on Application, User, or Status. Groups combine with OR, and conditions inside a group combine with AND.
  • Limit: Maximum number of entitlements to return (default 100, maximum 500).
If a filter group has no Status condition, Ravenna returns only Active entitlements for that group. Add a Status condition to include other states, such as Inactive or Failed Provisioning.Results include externally managed entitlements, which users hold through identity provider group membership. Their IDs start with synthetic-. Later steps can resolve these IDs like any other entitlement ID.Output data:
  • entitlementIds - Array of entitlement IDs matching the filter
  • userIds - Array of users holding the matched entitlements. Each user appears once, even if they hold several matching entitlements.
Common use cases:
  • Run a periodic access sweep with a Cron trigger
  • Pipe userIds into bulk user actions, such as the Okta Deactivate User or Remove Users from Groups actions
  • Notify the holders of an application’s access with Send Email, Add Followers, or Loop
Revokes one or more .Configuration:
  • Entitlements: The entitlements to revoke. Reference the entitlementIds output of Search Entitlements, or the entitlement from an Entitlement Status Changed trigger.
  • Revoke Note (optional): Why the entitlements were revoked.
Ravenna revokes the entitlements as your organization’s Ravenna bot user. If the revocation fails, the failure is recorded in the run log.Output data:
  • entitlementIds (Revoked Entitlements) - Array of the revoked entitlement IDs
Common use cases:
  • Clean up stale access on a schedule with Cron and Search Entitlements
  • Revoke access during offboarding

Asset actions

Create, update, find, and assign assets. Find these actions under the Asset group in the action picker.
Creates a new asset.Input fields:
  • Name and Asset Type - Required
  • Description (optional)
  • Status (optional) - Defaults to the organization’s default status
  • Assignees (optional) - Users or user groups to assign. User groups are expanded into their members.
Output data:
  • assetId (Created Asset) - The ID of the new asset
Common use cases:
  • Record hardware ordered through a procurement request
Updates an existing asset.Input fields:
  • Asset - The asset to update
  • Asset Type, Name, Description, and Status (optional)
  • Assignees (optional) - Replaces the asset’s current assignees with the selected users
Output data:
  • assetId (Updated Asset) - The ID of the updated asset
Common use cases:
  • Move an asset to In Repair when a repair ticket is opened
  • Hand an asset to a new holder in one step
Archives an asset. Archived assets are hidden from asset lists and can no longer be selected on tickets.Input fields:
  • Asset - The asset to archive
Output data:
  • assetId (Archived Asset) - The ID of the archived asset
Finds assets that match a set of filters.Configuration:
  • Asset Filter: One or more filter groups. Under Asset Type, open a type to filter on that type’s custom fields.
  • Limit: Maximum number of assets to return (default 50, maximum 50).
Output data:
  • assetId - The matching asset, when Limit is 1
  • assetIds - Array of matching asset IDs, for any other limit
Common use cases:
  • Find every asset a departing employee holds, then reassign them with Assign Asset
  • Pair with a Cron trigger to review assets in a given status
Changes who holds one or more assets.Input fields:
  • Assets - One or more asset IDs. Pass a single ID, a list, or a reference resolving to either, such as the assetIds output of Search Assets.
  • Strategy - How to apply the change:
    • Add assignees adds the selected users to each asset’s current assignees.
    • Remove assignees removes the selected users from each asset.
    • Set assignees replaces each asset’s assignees with exactly the selected users.
    • Clear removes every assignee.
  • Users - The users to add, remove, or set. Not needed for Clear. User groups are expanded into their members. Set assignees needs at least one user, and the step fails if the selected users and groups resolve to nobody.
Assigning and unassigning move the asset’s status automatically, as described in Statuses.Output data:
  • assetIds - The IDs of the assets that were updated
Common use cases:
  • Assign new hardware to an employee when an onboarding ticket is submitted
  • Clear assignees when an asset is returned to inventory

Tool actions

Calls an external API. Supports authentication with credentials stored in your organization’s . Find it under the Tool group in the action picker.Configuration:
  • URL - The API endpoint to call
  • Method - GET, POST, PUT, DELETE, or PATCH
  • Headers - Custom key-value headers
  • Query Parameters - Key-value pairs appended to the URL
  • JSON Body - Request body (for POST, PUT, PATCH, DELETE)
  • Timeout - Seconds to wait for a response. Defaults to 10, maximum 45.
  • Fail on error - Whether the step fails when the call fails. On by default. When off, the workflow continues with isSuccess set to false and the error in Response.Error.
  • Signature - Optional HMAC-SHA256 signing for outbound webhooks (see below)
Authentication methods:
  • None - No authentication
  • API Key - Sends a key in a configurable header (default X-API-Key), from a vault credential.
  • Bearer Token - Sends a token in the Authorization: Bearer header, from a vault credential.
  • Basic Auth - Sends a username and password as a Base64-encoded Authorization: Basic header. The password supports vault credentials.
Signature:Use the Signature section for outbound webhooks whose receivers verify requests with HMAC.
  • Signing Key - A vault credential holding the shared secret, encrypted at rest and decrypted in memory at request time.
  • Signature Header - The header that carries the signature. Defaults to X-Ravenna-Signature.
When a Signing Key is set and the request has a body, Ravenna computes HMAC-SHA256(body, secret), hex-encodes it, and sends it in the header. The signature covers the request body only, not the headers, URL, method, or query parameters. Requests without a body are sent without a signature. The receiver computes the same HMAC over the raw body with its copy of the secret and compares it to the header.Output data:
  • isSuccess - Boolean indicating whether the response status code is 2xx
  • Response.Body - The response body
  • Response.StatusCode - The HTTP status code
  • Response.Error - The error message when the call fails and Fail on error is off
Handling failures:By default, a failed call fails the step and stops the workflow. Turn off Fail on error to continue instead. The step returns isSuccess: false, Response.StatusCode: 500, and the error in Response.Error, so later steps can branch on the result, for example with an If / Else on isSuccess that posts Response.Error to Slack.Common use cases:
  • Send data to external systems
  • Fetch information from third-party APIs
  • Integrate with services that lack a native Ravenna integration
Ravenna sends Content-Type: application/json only when the request has a body. A GET, or a DELETE with an empty body, goes out with no Content-Type. Set the header yourself under Headers if an API needs it regardless.
Values inserted into single-line fields such as URL are used literally. Underscores, asterisks, and other markdown characters pass through unchanged, so a value like my_ticket_id produces a working URL.

Integration and Foundry actions

Connected integrations add their own actions to the picker, under each integration’s tile. See each integration’s workflow page from the Integrations overview.A Foundry action built for an integration Ravenna already supports, such as Google Workspace, appears on that integration’s native tile instead of its own, next to the built-in actions.
Last modified on November 18, 2026