Wait for AI-matched email or SMS

Explicit inboxes and phone numbers to search. A match in any listed source qualifies. At least one source is required; account-wide search is not implicit.

Optional semantic condition ANDed with deterministic match rules. Adding this field opts into metered AI evaluation. Omit it for existing deterministic behavior.

Optional filter for matching emails based on fields. For instance filter results to only include emails whose SUBJECT value does CONTAIN given match value. An example payload would be { matches: [{ field: 'SUBJECT', should: 'CONTAIN', value: 'Welcome' }] }. You can also pass conditions such as HAS_ATTACHMENT. If you wish to extract regex matches inside the email content see the getEmailContentMatch method in the EmailController.

Optional filter for matching SMS based on fields. For instance filter results to only include emails whose BODY value does CONTAIN given match value. An example payload would be { matches: [{ field: 'BODY', should: 'CONTAIN', value: 'Welcome' }] }.

JSON output schema for structured content repsonses. This schema dictates the format that an AI should use when responding to your instructions.

AI evaluator and execution limits. Tokens are weighted AI allowance units, shared across all candidates and expectations in a request. Confidence is model-reported, not a calibrated probability.