Overview

Pre-Publishing Rules in Sprinklr allow administrators to automate content checks, approvals, and tagging before messages are scheduled or published. By incorporating Outbound API Calls into Pre-Publishing Rules, you can integrate Sprinklr directly with your external systems such as legal/compliance engines, translation services, internal databases, or third-party approval portals prior to message release.

Key Use Cases

• Pre-flight Compliance & Content Moderation: Query an external corporate compliance database or AI governance endpoint to check for forbidden terminology, PII, or restricted phrases before the post goes out.

• External Workflow & Approval Triggering: Notify a downstream ticketing or third-party workflow tool immediately upon message submission.

• Metadata & Campaign Validation: Verify tracking IDs, UTM links, or external budget approvals from a centralized ERP/CRM system.

Configure an API Call in Pre-Publishing Rules

1. Navigate to Rule Engine via the Launchpad.

2. Select or create a Pre-Publishing Rule for your target workspace/account.

3. Under Conditions, set the criteria that determine when this API should be triggered (e.g., specific accounts, channels, or campaign tags).

4. Under Actions, locate and select Trigger Webhook / Invoke API Call.

5. Configure the request details:

   • Endpoint URL: Provide your target HTTP/HTTPS destination URL.

   • HTTP Method: Select POST, GET, PUT, etc.

   • Authentication: Select your pre-configured authentication profile (OAuth 2.0, API Key, Bearer Token, or Basic Auth).

   • Headers & Payload: Define custom headers and construct the JSON payload using message placeholders

     (example, {{message.text}}, {{message.id}}, {{campaign.name}}).

6. Configure Response & Failure Handling:

   • Success (2xx): The post proceeds through standard publishing/approval workflows.

   • Error (4xx / 5xx) or Timeout: Specify fallback behavior (e.g., block publication, set status to Draft, or alert the author via in-app notification).

7. Click Save and activate the rule.

Execution Behavior & Error Handling

Best Practices & Notes

• Latency Considerations: External APIs invoked during pre-publishing run synchronously or near-synchronously. Ensure your external endpoint responds quickly (< 2 seconds) to avoid delays in user publishing workflows.

• Audit Logs: Use Sprinklr Rule Execution Logs to inspect request payloads, headers, response status codes, and execution timestamps for troubleshooting.