Understand the available patterns for exporting and delivering data from Elaine.
Key concepts
- Exports can provide profile, membership, message, response, or project-specific data to approved downstream systems.
- Large or recurring datasets are commonly delivered asynchronously through controlled file exchange.
- API reads are appropriate when a caller needs a specific real-time object rather than a complete dataset.
How it works
- Define the consumer, purpose, fields, key, cadence, format, retention, and delivery location.
- Minimize columns and restrict rows to the approved scope.
- Use stable timestamps or run identifiers and document whether delivery is full or incremental.
- Validate record counts, schema changes, duplicates, and late delivery.
- Protect, expire, and delete exported files according to policy.
Governance and considerations
- Export schemas can evolve when configured data fields change.
- Downstream systems must handle additional columns defensively where the contract permits them.
- An export creates another copy of personal data and must be included in privacy governance.
Note
Exact UI labels, availability, and behavior can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.