Record System Pattern
The genie acts as a lightweight record system using Data Tables for CRUD operations, when an external system of record is unavailable or unnecessary.
Why This Pattern
The reasoning question is whether standing up or integrating a real system of record is worth it for this data. When the data is narrow-scope and low-volume, and doesn't need the guarantees a real SoR provides, a Data-Table-backed CRUD layer inside the genie is the pragmatic answer.
The trap: reaching for this when a real system of record already exists for the data, which quietly creates a second, unsynchronized source of truth.
When to Use It
- No suitable external system of record exists for the use case, or standing one up isn't justified.
- The data volume and complexity are modest enough for Data Tables to handle reliably.
When NOT to Use It
- A proper system of record already exists for this data — integrate with it directly rather than duplicating it.
- The use case requires complex relational data, heavy concurrent writes, or compliance guarantees a lightweight Data Table can't provide.
How It Works in Workato
- Create skills to perform CRUD operations against the underlying Data Table.
- Implement a mechanism to identify and trigger events on business objects as they change.
- Maintain role-based access control to the business objects the genie manages.
Source: Agentic Design Cookbook V2.0, p. 24