Augmentt Integration: Configuration
| NOTE: An authorized user account is required to run this integration. To support better security and audit visibility, we recommend creating a dedicated "service account" user. When configuring this integration, sign in using the service account rather than your personal user account to ensure that audit logs reflect the service account running the integration instead of the user who originally installed it. |
Complete the steps below to configure the Augmentt integration.
| NOTE: Before starting the configuration steps below, be sure you have completed the required prerequisite steps. See the Augmentt Integration: Prerequisites article for more information. |
- Click Admin on the sidebar menu and select Integrations Library.
- Click the Marketplace tab.
- Locate and select the Augmentt integration in the Security section of the marketplace.
- Click the Configure button.
- The Initial Configuration section is automatically populated. Click the Next button.
- On the Connections page, enter the settings described in the first table below, and then click the Next button.
- On the Alert Ticketing page, configure the settings described in the second table below. Then, click the Finish button. The integration creates the alert ticket type and the Augmentt Default customer if needed, and runs the first roster sync.
- Copy the webhook URL the integration created in the deploy log.
- Email Augmentt Support using Contact Us in the Augmentt portal. Include your webhook URL, the header name, which is Authorization unless you changed it, and your Augmentt Webhook Auth Value. Wait for Augmentt to confirm the webhook is turned on for your organization.
- In Augmentt, turn on the webhook for each tenant that should send alerts. Go to Secure > Alerts, select All Companies, open the Companies tab, and turn on the webhook icon for each tenant.
- Review the suggested tenant matches in Rev.io and confirm them. See the Augmentt Integration: Roster Sync article for more information.
- Trigger a test alert in Augmentt for a matched tenant, and check that a ticket appears in Rev.io on the right customer with the expected priority.
Each setting on the Connections page is defined below.
| Label | Definition |
| Rev.io PSA Connection | Filled in for you. No changes are needed. |
| Augmentt Reporting API Credential | Your Augmentt Access Key ID and Access Key Secret. This turns on the daily roster sync. If you leave it blank, alert ticketing still works, and you match tenants to customers manually. |
| Augmentt Webhook Auth Header Name | The name of the header Augmentt sends the secret value in. Leave this as Authorization unless Augmentt Support asks for a different name. |
| Augmentt Webhook Auth Value | The secret value that proves an alert came from Augmentt. Send the same value to Augmentt Support. If this is blank, every incoming alert is rejected until you set it. |
| Prod Mode | Connects the integration to your Rev.io production environment. Set this as directed by your Rev.io representative. |
| Debug | Turns on detailed logging for each alert. Leave this off unless you are working on an issue with Rev.io support. |
Each setting on the Alert Ticketing page is defined below. See the Augmentt Integration: Alert Ticketing article for more information about how these settings work.
| Label | Definition |
| Alert Ticket Type | The Rev.io ticket type used for every alert ticket. The default is Augmentt Alert, which is created automatically during setup if it doesn't exist. |
| Default Ticket Status | The Rev.io status new alert tickets open in. The default is New. Enter a status name that exists in Rev.io, because a ticket with a status name that doesn't exist is created without a status. |
| Default Bill Profile | The Rev.io bill profile for the Augmentt Default catch-all customer. The list shows your active bill profiles. |
| Severity Priority Map | Matches each Augmentt severity to a Rev.io priority, selected from your own priorities. Leave a row blank to use the standard match: High to P1, Medium to P2, Low to P3, and Informational to P4. |
| Minimum Severity | Alerts below this severity don't create tickets. The default is Informational, which creates a ticket for every alert. |
| Excluded Alert Types | Augmentt alert types that never create tickets, one type per row. Leave this blank to create tickets for every alert type. |
Augmentt doesn't sign its webhooks, so the secret value is how the integration confirms an alert came from Augmentt. Requests with a wrong or missing value are rejected, and the secret is never written to any log. Extra spaces at the start or end of the value are ignored.
For more information about the Augmentt integration, see the following articles.
Augmentt Integration: Overview
Augmentt Integration: Frequently Asked Questions