Settings
Overview
The Settings section allows you to configure your RCS integration, manage bots, and set up webhooks to receive event data.
From the left navigation menu, click Settings. Select General to view business and bot configuration options.
General Settings
The General Settings page displays your bot configuration and Google RCS integration details. In the General Settings section, you can view the following information:
Bot Selection
The setting is at the Bot level and not at the panel level, so it would differ from one bot to another.
| Section | Description |
|---|---|
| Google RCS Integration | Displays your API Key for Google RCS. You can copy it using the copy icon or view it using SHOW. Click SHOW and enter your panel's password to view the API key |
| Bot details | Displays your Bot ID, Business Display Name (Assistant Name), and Assistant ID. These values are required for bot-level integrations. |
Webhook Integration
Webhooks allow Netcore to send event data, such as message delivery, read status, and clicks, to your system in real time. The webhooks are at the bot level. If you select a different bot, the webhooks configuration is also changed.
| Column | Description |
|---|---|
| Name | The name assigned to the webhook for easy identification. |
| URL endpoint | The destination URL where webhook events will be sent. |
| Source key or callbackData | Additional parameters for validation or identification (optional). |
| Failure alert email | Email address where failure alerts will be sent if webhook delivery fails. |
| Status | Toggle to enable or disable the webhook. |
| Edit/Delete icons | Use to update or remove an existing webhook. |
Add a New Event Webhook
To add a new event webhook, follow the steps below
- Click + ADD EVENT WEBHOOK.
- Enter the following details:
| Field | Description |
|---|---|
| Name | Provide a unique name for your webhook. (Required) |
| URL endpoint | Enter the destination URL where event payloads will be sent. (Required) |
| Webhook header | Optional header parameters (for authentication, etc.). |
| Webhook failure alert email | Email to receive notifications for webhook failures. (Required) |
- Click TEST to verify connectivity.
- Click SAVE to activate the webhook.
Account Settings
Use this to enable/disable link tracking and add a custom domain. This feature is primarily used for Customer Engagement(CE).
- Link Tracking: When link tracking is enabled, Netcore wraps your original URL with a shortened tracking link. Once a customer clicks the link, the click is first recorded on Netcore’s server. After tracking, the customer is redirected to the original destination URL.
- Custom Domain: You can configure your own domain instead of using the default Netcore link, making the shortened URLs look more branded and trustworthy.
Best Practices
- Use Descriptive Names: Make it easy to identify webhooks by their purpose. For example, Order_Status_Update_Webhook
- Monitor Failures: Keep failure alerts enabled to catch and resolve issues quickly.
- Secure Endpoints: Protect your webhook URLs with authentication headers.
- Test Before Going Live: Always use the TEST button to ensure proper delivery before enabling for production campaigns.
Updated 2 days ago