Skip to content
  • There are no suggestions because the search field is empty.

User Automation Overview

Configure scheduled macros, notice macros, and external listeners to automate your user management workflows

The User Automation page is where you put your user macros into motion. While macros are built in User Resources, User Automation is where you define when and how those macros run — whether on a recurring schedule, automatically upon user login, or triggered by an external system. Together, these three tools let you reduce manual effort and keep your user management workflows running consistently in the background.

User Automation exists at both the community and project levels of Centercode. The community-level version is accessed via Community menu > Community management > Users > User automation, and governs automation that applies to users across your entire community.

The project-level version is accessed via Management > Users > Project users > User automation, and is scoped exclusively to users within that project. Automation configured at one level has no effect on the other, so you may find yourself setting up parallel schedules and listeners depending on where your workflows live.

Scheduled User Macros

The Scheduled User Macros section lists all macros that have been configured to run automatically on a defined schedule. Use the Create a macro schedule button to set up a new scheduled macro. For step-by-step guidance, see How do I create, modify, or remove User Macro Schedules?

Each scheduled macro row displays the following columns:

Name: The label for the macro schedule. Clicking the row opens it for editing.

Frequency: How often the macro will run — options include once, hourly, daily, weekly, or monthly.

Next run: A relative timestamp showing when the macro is next set to execute.

Last modified by: The admin who most recently saved changes to the schedule.

Hovering over a scheduled macro row reveals two additional options:

Toggle on/off: Enables or disables the macro schedule without removing it. A schedule that is toggled off is considered inactive and will not execute until toggled back on. Use this option when you want to temporarily suspend a schedule without losing its configuration.

Remove: Permanently deletes the macro schedule. This action cannot be reversed.

💡 Ted Tip: I recommend scheduling macros to run during off-peak hours whenever possible. Macro schedules — especially those targeting large user sets — can impact site performance when executed simultaneously with other scheduled tasks like report distributions. Staggering your schedule times is a simple way to keep things running smoothly.

Notice Macros

The Notice Macros section lists all macros that have been injected into the notice chain to trigger automatically when users log in. Use the Create a notice macro button to add a new one. For a deeper look at how notices and notice macros work, see the Macros & Automation FAQ.

Unlike scheduled macros, notice macros fire based on user access rather than a set time. Each time a qualifying user logs in, the notice chain evaluates whether the notice macro's conditions are met and executes accordingly. Notice macros can be configured as static (running for all users on specified teams) or conditional (running different macros based on whether a user matches a defined filter).

Each notice macro row displays the following columns:

Name: The label for the macro schedule. Clicking the row opens it for editing.

Hovering over a notice macro row reveals the additional option:

View log: Takes you to a log of every time this notice macro has executed.

User External Listeners

The User External Listeners section lists all API endpoints configured to receive incoming requests from external systems and trigger user-level actions in Centercode. Use the Create an external listener button to add a new one. For step-by-step guidance on setting up a listener, see the Simple Guide to External Listeners.

An external listener acts as a doorway for third-party tools — such as Zapier, Jira, or custom-built systems — to interact with Centercode via webhook. When an external system sends a request to the listener's API endpoint, Centercode executes the associated action against the targeted user. Listeners support three action types: executing a macro, adding a comment to a user account, or storing external data against a user record.

Each external listener row displays the following columns:

Name: The internal label for the listener. Clicking the row opens it for editing.

Last modified by: The admin who most recently saved changes to the listener.

Hovering over an external listener row reveals two additional options:

Toggle on/off: Enables or disables the listener without removing it. A listener that is toggled off will not respond to incoming requests until toggled back on. Use this when you need to temporarily pause an integration without dismantling it.

Remove: Permanently deletes the external listener. This action cannot be reversed.

💡 Ted Tip: I recommend always adding a Filter to your external listeners when the associated macro performs a destructive action like removing users. A filter ensures the listener will only execute against users who meet your defined criteria, protecting administrative accounts or other teams from being affected if your external system sends an unexpected request.

Notes

  • The Schedule User Macros role is required to create or manage macro schedules. External listeners require Enhanced Integrations to be enabled on your account, along with a community-level API key.
  • Macro schedules and external listeners that are toggled off will not execute, but their configurations are preserved and can be reactivated at any time.