rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Actions

Last updated Automation

AI summary

Automation actions are individual steps an automation runs, such as sending messages or creating tickets. Find setup guides for complex actions and a reference of all actions per connector.

An automation action is one step an automation runs, such as sending a message, creating a ticket or changing an object. These guides show how to set up the actions that need more than a few clicks: Teams notifications, ServiceNow tickets, Power Automate webhooks, archiving teams, removing old SharePoint file versions and deleting Claude projects. The automation actions reference lists every action per connector.

Start with

  1. Send a Teams notification for policies Post policy results to a Teams channel through a Teams webhook.
  2. Create ServiceNow tickets with an automation Open a ServiceNow ticket from an automation.
  3. Archive or unarchive a team with an automation How to add the Archive or Unarchive a Team action to an automation, and how the Archive Unused Teams template uses it.
  4. Automation actions reference Every action a Rencore Governance automation can run, grouped by connector, with the number of actions for each one.

All guides in actions

Notify people and open tickets 3 guides

Post to Teams, call a Power Automate flow, or open a ServiceNow ticket.

  • Send a Teams notification for policies

    Post policy results to a Teams channel through a Teams webhook.

    Before you begin: Your Rencore role includes the Create Automation permission. (+2 more)

    13 steps

  • Trigger a webhook for Power Automate

    Call a Power Automate flow or another webhook from an automation.

    Before you begin: Your Rencore role includes the Create Automation permission. (+1 more)

    10 steps

  • Create ServiceNow tickets with an automation

    Open a ServiceNow ticket from an automation.

    Before you begin: Your Rencore role includes the Create Automation permission. (+1 more)

    10 steps

Change objects 3 guides

Archive a team, trim file versions or delete a Claude project.

  • Archive or unarchive a team with an automation

    How to add the Archive or Unarchive a Team action to an automation, and how the Archive Unused Teams template uses it.

    Before you begin: Your Rencore role includes the Create Automation or Edit Automation permission. (+1 more)

    5 steps Watch it · 5 min Teams

  • Remove SharePoint file versions

    This automation action deletes older major or minor versions of a SharePoint file, always keeping the current version…

    Before you begin: Your Rencore role includes the Create Automation or Edit Automation permission. (+1 more)

    8 steps Watch it · 4 min SharePoint

  • Delete a Claude project

    This automation action permanently deletes a Claude project, including its custom instructions and knowledge…

    Before you begin: Your Rencore role includes the Create Automation or Edit Automation permission. (+4 more)

    5 steps Watch it · 4 min Claude Enterprise

Frequently asked questions

What is an automation action in Rencore Governance?

An automation action is one step an automation runs, such as sending a message, creating a ticket or changing an object.

How can I send policy results to a Teams channel?

Use the Teams webhook guide to post policy results to a Teams channel from an automation. Your Rencore role must include the Create Automation permission.

Can an automation call a Power Automate flow?

Yes. An automation can trigger a webhook to call a Power Automate flow or another webhook. Your Rencore role must include the Create Automation permission.

Which permission do I need to archive or unarchive a team with an automation?

Your Rencore role must include the Create Automation or Edit Automation permission. The Archive Unused Teams template also uses the Archive or Unarchive a Team action.

Which actions change objects instead of only sending notifications?

Archive or unarchive a team, remove SharePoint file versions and delete a Claude project all change objects. The SharePoint action deletes older major or minor versions and always keeps the current version.