Table relationships
Model relationships between table rows, CRM records, and workflow context so automation has the right operating data.
Use this Studio state to connect the product UI to a real business operation: customer signal, agent behavior, workflow path, channel, CRM context, and review outcome.
Summary
Model relationships between table rows, CRM records, and workflow context so automation has the right operating data.
Concepts covered
Step breakdown
- Open TablesStart in the Tables area and confirm what the real screen is showing.
- Inspect product behaviorUse screenshots and visible product states to understand what the screen does, why it exists, and how teams use it.
- Connect the platformSee how the screen connects to agents, workflows, records, activity, channels, integrations, or ownership.
Why relationships matter in tables
A table row becomes more useful when it connects to another entity. A campaign row can reference a CRM Segment. A territory row can reference the owner's CRM Person record. A routing rule can point to a workflow or agent.
Relationships let a single table serve as the lookup layer across multiple workflows without duplicating the data.
Modeling relationships in practice
Use a field to store a reference ID — a CRM person ID, company ID, or another table row ID. When the workflow reads the table, it can use that reference to look up the related CRM record and attach the full context to the next AI or routing step.
Example: a 'Qualified Leads' table stores a person ID, qualification score, assigned owner ID, and follow-up status. A workflow reads the table row, then looks up the CRM Person using the stored ID to get the full contact context before sending a personalized follow-up.
Keeping relationships current
Table relationships decay if records change. When a CRM record is updated, merged, or deleted, any table that references it by ID should be reviewed.
Build update logic into workflows: when a deal stage changes or a person is reassigned, use a Table Action node to update the relevant reference in the connected table.
Operational playbook
Use Table relationships as part of the Frontline Studio Tables operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Table relationships teach?
Model relationships between table rows, CRM records, and workflow context so automation has the right operating data.
How should teams use this lesson?
Use it as a product walkthrough: understand the real screen, the product behavior, the operational outcome, and how the area connects with the rest of Frontline.
When should I use Tables instead of CRM?
Use Tables for operational reference data such as routing rules, campaign lists, lookup values, or lightweight state. Use CRM for customer records and relationship context.
How do Tables connect to workflows?
A workflow can read a table, update a row, append an event, or use table values in routing, AI prompts, and integration payloads.
What makes table data AI-ready?
Use clear column names, stable values, documented meaning, and explicit relationships to records or workflow context. AI and deterministic nodes both benefit from predictable structure.