Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

How to remove runbook via automation

Hello!

I have a project I am working on to capture the "second response time" of a ticket. After some testing I figured I could accomplish this via runbooks, API, and automation rules. I have another runbook executing in a similar way via a 5-step API runbook to relate the requester's computer to the current ticket via Entra and the current signed-in user. Its been --mostly-- working as intended, but since this runbook is present, the second response time runbook cannot be attached to the ticket.

Do you know of a way I could insert a step at the beginning / end of the process integration steps to have the runbook remove itself? I am thinking if the first / last step of every runbook removes the runbook, we can get around this challenge. Or if there was a way to attach multiple runbooks to an incident, or even if this could be simplified into a single step process, then we could execute via automation rules instead of relying on runbooks for this.

Find more posts tagged with

Active

system automation

api integration

process integration

runbooks

runbook_automation

Status: Active

Comments

joeybrown

Hi @BarnDarn

This request makes perfect sense and something we will look to adding in the future when we continue our work on expanding our automation functionality. Speaking of expanding our automation functionality, we recently introduced the ability to run process integrations via automation rules. With this you can easily send a payload to clear the assignee.

Here is a quick example of what you will want to do to accomplish this:

Create an automation rule based on the conditions needed or add this to the already existing automation you have in place.

Setup the process integration with credentials of SWSD

Your endpoint https://api.samanage.com/incidents/{{context_id}}.json with the Method being PUT

The headers will be Accept: application/vnd.samanage.v2.1+json and Content-Type: application/json

The payload is {
"incident": {
"assignee_id": ""
}
}

I tested this in my environment and it works perfectly. Hope this works for you while we work through the backlog of adding this to the automation rules.

BarnDarn

Thank you for this. I got this working.

In an attempt to duplicate the ticket type to submit an additional feature request, I accidentally edited and replaced this feature-requests contents.

This can be closed out, thank you

Original context: how to unassign an incident from a user via automation rules.