The Actions tab on Moderation Dashboard allows you to create custom user and post actions that can either be triggered manually by a moderator, or automatically through matching rules you’ve defined. This is where you define any enforcement actions that you’d want to take to moderate your platform, such as removing a post, tagging a post, suspending a user for a period of time, or banning a user. Actions serve as the communication pipeline between Moderation Dashboard and your application server.

Create & Test Actions

ℹ️

Actions may trigger multiple times

Please note, your actions server should expect multiple action triggers for a given user or post due to:

• Multiple rule triggers for a user or post
• Failed action retry

The actions you create tell Moderation Dashboard how to communicate with your platform when content triggers moderation rules. When defining an action, you must specify a callback URL (e.g. a webhook) that, when hit, implements that action in your application. When the action is triggered, Moderation Dashboard will ping your callback server with the required metadata so that you can successfully execute the action on the correct user or post within your platform.

You can customize the POST request we send to your server when creating an action:

• Endpoint URL (Callback, Required): This is the URL we will ping when an action is triggered on Moderation Dashboard. Note: URLs do not need to be unique between actions. For instance, you can use metadata, keys, etc. to differentiate.
• Auth Header/Value: You can specify an Authorization header and token value (if your server requires one) so Moderation Dashboard can communicate with the server.
• Query Params: Moderation Dashboard will send all user and post metadata in the query parameters of the request. You can customize the key name to match your naming convention.

Below is a sample JSON response.

{
  "user_id": "123",
  "post_id": "123",
  "rule": "delete"
}

📘

HTTP Status Response

Moderation Dashboard expects an HTTP 200 OK success status response code to verify that the action has been taken. Any other response code will be treated as a failed action and will show up in the Moderation History (see below).

For failed actions, we recommend that response.data/body is an object. When creating an action, you should use the Test Action feature to ensure that your action is pinging the proper endpoint with correct metadata.

Actions in Moderation History

Moderation History shows all moderation events on Moderation Dashboard, including content creation, successful and failed actions, rules triggers and more.

You can filter for specific actions:

Filter by completed or failed status:

And even view the response message from your callback servers from those actions, to debug why the actions failed to begin with: