# Invoking AI transformers

You can call AI transformations on emails, attachments, SMS or any content directly from code and tests.

## Invocation options
Choose the input type that matches your workflow:

- Email-centric workflows: invoke on received email content from your inboxes.
- Attachment-centric workflows: invoke on uploaded files or email attachments.
- SMS-centric workflows: invoke on inbound SMS where structured extraction is needed.
- Generic text workflows: invoke on arbitrary content when you already have the payload in your application.

## Recommended flow
1. Define your schema and extraction intent in [AI transformers](/docs/ai-transformers/).
2. Validate output fields in [output schemas](/docs/output-schemas/) before production use.
3. Invoke the transformation from your test or application flow.
4. Route results to dashboard review, API retrieval, or [webhooks](/docs/webhooks/).
5. Iterate on prompt/schema design using real examples from failed or partial extractions.

## Practical guidance
- Start with a narrow schema (fewer required fields) and expand once extraction is stable.
- Prefer deterministic field names and explicit formats for dates, currency, and identifiers.
- Keep transformer definitions close to the business process that consumes the results.

## Next pages
- [Manage results](/docs/ai-results/)
- [Output schema design](/docs/output-schemas/)
- [AI overview](/docs/ai/)