Custom Conditions

Define custom conditions to control when webhooks are triggered. Use complex logic to ensure keys are only generated for specific purchase scenarios.

1

Condition Types

String Conditions

• Contains: Check if field contains text

• Equals: Exact string match

• Regex: Pattern matching

• Exists: Check if field exists

Logic Operators

2

Field Paths

Use dot notation to access nested fields in the webhook payload:

Examples:
item.quantity - Access quantity field
customer.email - Access customer email
payment.status - Access payment status
metadata.product_id - Access nested metadata

3

Example Conditions

Simple Condition:
Generate keys only for premium products:

Field:
item.type
Condition:
equals "premium"

Complex Condition:
Generate keys for successful payments with specific quantity:

Group 1 (AND):
payment.status equals "completed"
item.quantity greater_than 0
Group 2 (OR):
item.type equals "premium"
item.type equals "standard"

Pro Tip: Start with simple conditions and gradually add complexity. Use the test webhook feature to verify your conditions work as expected.