Skip to main content

Advanced Flows (Beta)

Flows is Claimify's next-generation visual automation builder. While our standard Automations follow a linear priority-based system, Flows allow you to build complex, branching logic to handle your claims exactly how your business requires.

Beta Feature

Flows is currently in Beta. We are actively adding new nodes and integrations. If you have feedback, please reach out at supprt@xco.agency.

What are Flows?​

Flows are node-based diagrams that represent your claim lifecycle. Each flow consists of:

  1. Trigger: The event that starts the flow (e.g., "Claim Created").
  2. Nodes: Blocks that perform logic or actions.
  3. Edges: The lines connecting nodes, defining the path the claim takes.

Node Types​

1. Triggers​

The starting point of any flow.

  • Claim Created: Fires immediately when a customer submits a new claim form.

2. Logic & Conditions​

  • Condition Node: Branch your flow based on claim data.
    • Example: If Order Total > $100 -> Go to Manager Review. If not -> Auto Approve.
  • Wait/Delay: (Coming Soon) Pause the flow for a specific duration.

3. Actions​

Perform operations on the claim or external systems.

  • Update Status: Move the claim to any of your Custom Statuses.
  • Process Refund: Automatically trigger a Shopify refund.
  • Create Reorder: Automatically create a Shopify replacement order.
  • Klaviyo Integration: Send data to Klaviyo to trigger a branded email or add a tag.
  • Shopify Flow Action: Trigger an external Shopify Flow.

Using Templates​

To help you get started, we provide several Pre-built Templates:

  • Auto-Approve Low Value: Automatically approve and refund claims under a certain dollar amount.
  • VIP Routing: Identify high-value customers and route their claims to a priority queue.
  • Damaged Item Evidence Gate: Automatically request more info if photos are missing for "Damaged" reasons.

Managing Your Flows​

Draft vs. Active​

  • Draft: New flows are created in Draft mode. They will not execute on incoming claims.
  • Active: Once you are happy with your logic, toggle the "Active" switch.

Execution History​

Each flow has a "Recent Runs" tab where you can see:

  • Which claims triggered the flow.
  • The path taken through the nodes.
  • Success or failure status of each action.

Best Practices​

  • Test with Samples: Before activating a flow, use the "Test Flow" feature to see how it would handle a specific past claim.
  • Keep it Clean: Use the "Auto-Layout" button to keep your nodes organized.
  • Safety First: For high-risk actions like "Process Refund", always add a condition to check for fraud or high order values.