When to Use Third-Party Automation vs Native Notion Automations
Learn when to use native Notion database automations versus third-party tools like Zapier and Make for your workflow automation needs.
Notion Database Relations Explained: Build Connected Recruiting Workflows
Master Notion database relations to build connected recruiting workflows. Learn two-way relations, rollups, and automation with real recruiting examples.
TABLE OF CONTENTS
Notion database relations are the superpower for connecting information across multiple databases. Instead of duplicating data or maintaining separate spreadsheets, relations let you build a single source of truth that automatically updates everywhere.
For recruiting productivity workflows, relations connect candidates to positions, positions to clients, and tasks to both. Information flows in both directions — open a candidate and see their positions; open a position and see all candidates under consideration.
What Are Notion Database Relations?
A relation property creates a link between two databases. When you add a relation in one database, Notion can automatically create a reciprocal relation in the other database.
Example: When you relate a Candidate to a Position, Notion creates:
- A "Positions" property in your Candidates database
- A "Candidates" property in your Positions database
Click on any candidate to see their positions. Click on any position to see all candidates being considered.
One-Way vs Two-Way Relations
When creating a relation, Notion asks if you want a two-way relation.
One-Way Relation
The relation property only appears in the database where you created it. You can navigate from Database A to Database B, but not back.
Use case: Reference data that doesn't need back-linking, like relating tasks to a project template library.
Two-Way Relation (Recommended)
The relation property appears in both databases, creating bidirectional navigation.
Use case: Nearly everything in recruiting. You want to see positions from a candidate page AND see candidates from a position page.
Creating Your First Relation
Let's connect a Candidates database to a Positions database.
Step 1: Add the Relation Property
In your Candidates database:
- Add a new property
- Select "Relation" as the property type
- Choose your Positions database
- Enable two-way relation
- Name it "Positions"
Notion automatically creates a "Candidates" relation in your Positions database.
Step 2: Link Items
Open any candidate page. In the Positions property, click to add. Search for and select the position they're being considered for.
Now open that position's page. The candidate automatically appears in the Candidates property — the two-way relation keeps both sides in sync.
Step 3: Add More Relations
Create additional relations:
- Tasks → Candidates
- Tasks → Positions
- Positions → Clients (if you separate clients from positions)
Each relation creates a connection point where information flows.
Understanding Rollups
Rollups calculate values from related database items. They answer questions like:
- How many tasks does this candidate have?
- What percentage of tasks are complete?
- What's the total value of positions this client has open?
Creating a Progress Rollup
In your Candidates database, add a rollup property:
Configuration:
- Relation: Tasks (the relation property connecting to your Tasks database)
- Property: Status
- Calculate: Percent checked
This rollup shows what percentage of a candidate's tasks are complete, automatically updating as you check off tasks.
Other Useful Rollups for Recruiting
Count of open tasks:
- Relation: Tasks
- Property: Status
- Calculate: Count values
- Show original: Filter to only count "Not Started" or "In Progress"
Most recent activity date:
- Relation: Tasks
- Property: Last edited time
- Calculate: Latest date
Total interviews scheduled:
- Relation: Tasks
- Property: Task name
- Calculate: Count values
- Show original: Filter to tasks containing "Interview"
Relation Limits
Some relations should be limited to prevent errors.
Setting Relation Limits
When creating a relation property, you can set a maximum number of related items.
Example: A candidate should only have one "Current Position" but can have many "Interview Tasks."
Set a limit of 1 on the "Current Position" relation. Set no limit on "Interview Tasks."
When to Use Limits
Limit to 1:
- Current status
- Assigned recruiter
- Primary contact
No limit:
- Past positions
- Related tasks
- Interview rounds
Chaining Relations
Relations can reference other relations, creating powerful data flows.
Example: Client Information on Candidate Pages
You have:
- Candidates → Positions (relation)
- Positions → Clients (relation)
Create a rollup in Candidates:
- Relation: Positions
- Property: Clients (the relation property in Positions)
- Calculate: Show original
Now candidate pages display client information without direct Candidate → Client relations.
Multi-Hop Rollups
Rollups can calculate on related relations:
Example: Show total number of candidates across all positions for a client.
In Clients database:
- Relation: Positions
- Create rollup on Positions → Candidates relation
- Calculate: Count unique values
This chains through Clients → Positions → Candidates to count total candidates.
Using Relations in Automations
Database automations use relations to create connected workflows.
Auto-Create Related Tasks
Trigger: When position is added to candidate
Action: Create task in Tasks database
- Set Task → Candidate relation to the triggering candidate
- Set Task → Position relation to the newly added position
The automation uses relation context variables to automatically link tasks to the right candidate and position.
Conditional Automation Based on Relations
Trigger: When candidate status changes to "Offer Extended"
Condition: Only if candidate has relation to "Executive Search" position type
Action: Create specialized onboarding tasks
The automation checks the related position's properties before executing.
Synced Blocks vs Relations
Don't confuse synced blocks with relations.
Synced blocks: Copy the same content to multiple pages. Changes sync everywhere. Used for content, not data.
Relations: Link database items together. Used for structured data and workflows.
Use synced blocks for: Standard interview questions, company policies, email templates.
Use relations for: Connecting candidates to positions, tracking relationships.
Common Relation Mistakes
Relating the Wrong Databases
Relate Tasks to Candidates, not Tasks to a random page that lists candidates. Relations work between databases, not between pages and databases.
Creating Relations Instead of Properties
If every candidate needs a "Years of Experience" field, create a number property, not a relation to a "Years of Experience" database. Relations are for linking distinct items, not for attributes.
Forgetting to Use Relations in Automation
When automations create database items, explicitly set relation properties. Don't assume Notion knows which candidate or position the new task belongs to.
Not Setting Up Two-Way Relations
Almost always use two-way relations. The rare exceptions are reference libraries or templates where back-linking creates clutter.
Displaying Relations in Views
Inline Relation Display
In table views, relation properties show as clickable links. Hover to preview, click to open.
Grouping by Relations
Create board or table views grouped by relation properties:
- Group Tasks by Candidate to see all work per person
- Group Candidates by Position to see your pipeline
- Group Positions by Client to understand client load
Filtering by Relations
Filter database views by relation properties:
- Show only candidates related to high-priority positions
- Show only tasks related to candidates in "Interview" status
- Show only positions related to "Active" clients
Advanced Relation Patterns
Self-Referencing Relations
A database can relate to itself.
Example: Tasks database with "Parent Task" and "Sub-Tasks" relations to the same Tasks database.
This creates task hierarchies without separate databases.
Many-to-Many Relations
Most recruiting relations are many-to-many:
- One candidate can apply to many positions
- One position can have many candidates
- One task can relate to many candidates (group interviews)
- One candidate can have many tasks
Notion handles this naturally. No junction tables required.
Polymorphic Relations (Workaround)
Notion doesn't support true polymorphic relations (relating to different database types in one property).
Workaround: Create separate relation properties for each database type, then use a formula to combine them in display.
Database Relations vs Linked Database Views
These are different features:
Database relations: Connect items between databases using relation properties.
Linked database views: Display the same database in multiple locations with different filters/views.
Use both together: Create a candidate page with a linked view of the Tasks database filtered to show only that candidate's tasks (using the relation as the filter).
Troubleshooting Relations
Relation Property Shows Empty
Check:
- Is the related database deleted?
- Do you have permission to view the related database?
- Did you link any items yet?
Can't Find Database in Relation Picker
Make sure:
- The database exists (not deleted)
- You have access to the database
- You're creating a relation property (not selecting relation items)
Changes Don't Sync in Two-Way Relations
This shouldn't happen with proper two-way relations. If it does:
- The relation might be one-way only
- You might be looking at an old page version
- Refresh the page
Getting Started with Relations
Start with one simple relation:
- Create two databases (Candidates and Positions)
- Add a two-way relation between them
- Link 2-3 test items
- Navigate both directions
- Add a simple rollup
Once comfortable, add your Tasks database and additional relations.
Need help building connected workflows? Book a free consulting call to verify if Notion database relations will solve your workflow challenges.
Related Posts
What Can Notion Replace? Slack, Excel, and Microsoft Teams Compared
Wondering what Notion actually replaces? Compare Notion to Slack, Excel, and Teams—learn what to switch, what to keep, and how to connect the tools you still need.
Build a Notion Task Tracker for Small Marketing Teams
Build a Notion task tracker for your marketing team: assign requests, set deadlines, create filtered views, and connect with Slack. No code needed.
