Back to Changelog
Back to Changelog

June 22, 2023

Others

Integrate With External Systems via HTTP Client

Integrate With External Systems via HTTP Client

📲 Call External APIs from Rootly

We are thrilled to introduce a new addition to our ever-growing list of workflow tasks: the HTTP Client task! With this latest addition, organizations can now make outbound request calls to external APIs directly within their workflows.

Here are the key highlights of the HTTP Client task:

  • Seamless Integration via Workflows: The HTTP Client task seamlessly integrates into your workflows, enabling you to incorporate external API calls to your incident response automation. Whether you need to retrieve data or perform write actions, this task has you covered.
  • Versatile HTTP Methods: The new task supports a wide range of HTTP methods, including GET, POST, PUT, and more. You’re well-equipped to find the appropriate operation for the API you're interacting with.
  • Flexible Request Parameters: You can specify headers, query parameters, and request bodies to match the unique contract of each external API.
  • Heightened Security with Secrets: Rest assured that your API calls are secure and reliable. You can leverage Rootly Secrets to reference API keys, tokens, etc. to ensure that sensitive data is never exposed at any point in the call.

The new HTTP Client task opens up a whole new world of possibilities for integrating with external services and systems. Common enterprise use cases are all just a workflow task away!

  • Event logging can be supported by firing off an API call to an external audit service each time a workflow is run in Rootly.
  • Asynchronous run jobs can be triggered to write to a data warehouse every time an incident is created or updated.
  • Incidents can be redirected to other Rootly orgs by calling Rootly APIs with org-specific API keys

Checkout this instructional video on how to get started with setting up an HTTP Client task.

🌝 New & Improved

🆕 Added Update Notion Page task to enable overwriting of an existing Notion page
🆕 Introduced the ability to turn user mentions off on timeline events to reduce notification noise
💅 Enhanced Form Fields page for better displaying of fields with extended names
💅 Improved role assignment logic for requesting permission upgrades to ensure accuracy
🐛 Fixed datepicker display issue on web UI
🐛 Fixed inability to delete previously added action items in Send Slack Message task

Previous post
Previous post
You are viewing the latest post

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Introducing: Rootly x ClickUp! Our New Integration for Seamless Collaboration and Task-Tracking

The New and Improved Home Dashboard

Guided Onboarding Flow for New Rootly Users

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup