Skip to main content
Conditions are rules that control which entities are included in or excluded from processing. They act as a filter applied before data is acted upon.

​
Where conditions apply

Conditions can be configured at two levels:
LevelScope
System IntegrationApplies to all data handled by that integration, across all domain mappings that belong to it.
Domain MappingApplies only to data flowing through that specific domain mapping.
If both levels have conditions configured, both must be satisfied for an entity to proceed. Integration-level conditions are evaluated first.

​
Condition rules

A condition is made up of one or more rules. Each rule evaluates a property on the entity against a value using an operator. Common operators include:
  • Equal to / not equal to
  • Contains / does not contain
  • Is set / is not set
  • Greater than / less than (for numeric and date properties)
Rules can be combined with AND (all rules must pass) or OR (any rule must pass) logic.

​
Active status filtering

A common use of conditions is filtering by employment status. For example, a destination payroll system may only need to receive active employees. Rather than manually maintaining this list, a condition on active_status ensures that terminated employees are automatically excluded. When an employee’s status changes to terminated, Twine will stop replicating updates for that entity to any mapping that has an active-only condition configured.