Intro

This is a workflow where anytime an incoming message is received, an HTTP request will be triggered. You can add filters to the workflow so the HTTP request is only triggered when certain criteria are met (e.g. message contains ‘hello’).

This allows you to send data from Clerk Chat to another application and do something with that data.

Use cases

1. Healthcare - Patient Symptom Triage
   When a patient messages with keywords like "pain," "fever," or "emergency," the workflow triggers an HTTP request to the hospital's triage system, automatically creating a preliminary assessment and alerting the appropriate medical staff.

2. Manufacturing - Equipment Maintenance Alerts
   When machine operators send messages containing "malfunction," "breakdown," or specific error codes, the workflow sends an HTTP request to the maintenance management system, creating immediate work orders and notifying technicians.

3. Financial Services - Fraud Detection Response
   When customers message about "unauthorized transaction" or "suspicious activity," the workflow triggers an HTTP request to the bank's fraud detection system, immediately freezing the account and initiating the investigation protocol.

4. Hospitality - Room Service Automation
   When hotel guests message "room service" followed by specific menu items, the workflow sends an HTTP request to the kitchen management system, automatically creating orders and updating inventory.

5. E-commerce - Price Match Guarantee
   When customers send messages containing "price match" and a competitor URL, the workflow triggers an HTTP request to a price comparison API, automatically validating the claim and generating approval for price adjustments.

6. Education - Assignment Submission Tracking
   When students message with "submit assignment" and attach files, the workflow sends an HTTP request to the learning management system (LMS), automatically logging submission times and updating grade books.

7. Real Estate - Property Viewing Coordination
   When prospects message with "schedule viewing" and specific property codes, the workflow triggers an HTTP request to the agency's scheduling system, checking agent availability and property access times.

8. Automotive - Service Appointment Booking
   When customers message about "oil change," "maintenance," or specific service codes, the workflow sends an HTTP request to the dealership's service management system, checking availability and creating appointments.

9. Insurance - Claim Initial Processing
   When policy holders message with "file claim" and incident details, the workflow triggers an HTTP request to the claims processing system, creating a claim number and initiating the assessment workflow.

10. Retail - Inventory Check Automation
    When customers ask "do you have" followed by specific product SKUs, the workflow sends an HTTP request to the inventory management system, checking real-time stock levels across all locations and automatically responding with availability.

Template

Example
JSON
Copy
{
  "$schema": "https://web-api.clerk.chat/pipeline-schema",
  "name": "HTTP Request Workflow",
  "nodes": [
    {
      "type": "tool_runner",
      "name": "Edit your HTTP request here",
      "triggeredBy": [
        "unreadMessage.fromAny"
      ],
      "responseType": "json",
      "nodeConfig": {
        "type": "web_tools",
        "config": {},
        "enabledTools": [
          "json_request"
        ],
        "tools": {}
      }
    },
    {
      "type": "trigger",
      "name": "Start",
      "triggeredBy": [
        "userMessage"
      ],
      "responseType": "json"
    }
  ],
  "edges": [
    {
      "name": "Add your filter here",
      "sourceNode": "Start",
      "destinationNode": "Edit your HTTP request here",
      "sourceVariables": null,
      "filters": []
    }
  ]
}