Configure Property Mappings
Property mappings control how data from an email gets saved into your destination. Each mapping connects an email field (like the subject line) to a Notion property or Google Sheets column. Without mappings, Quicktion won't know where to put the email data.
How to Set Up Mappings
- Go to your Destinations page in the Quicktion dashboard
- Click on the destination you want to configure
- Scroll to the Property Mappings section
- For each Notion property you want to populate, select the email field that should fill it
- Save your changes
You can add as many mappings as you need. Each Notion property can only be mapped to one email field.
Available Email Fields
These are the email fields you can map to your Notion properties:
| Email Field | Description |
|---|---|
| Subject | The email subject line |
| Sender | The sender's display name |
| Sender Email | The sender's email address |
| Date | The date and time the email was sent |
| Body | The full email body, converted to rich text or page content |
Compatible Notion Property Types
Not every email field works with every Notion property type. Here's what's compatible:
| Notion Property Type | Compatible Email Fields |
|---|---|
| Title | Subject, Sender, Sender Email |
| Rich Text | Subject, Sender, Sender Email, Body |
| Sender Email | |
| URL | Sender Email |
| Date | Date |
| Select | Subject, Sender, Sender Email |
| Multi-select | Subject, Sender, Sender Email |
| Checkbox | (use default values instead) |
| Number | (use default values instead) |
The Body field is special. When mapped to a Rich Text property, the email body is condensed into that property. When no Rich Text mapping exists for the body, the full email content is added as page content (Notion blocks) inside the created page.
Common Mapping Examples
Basic email log
Map your database properties like this:
- Name (Title) ← Subject
- From (Rich Text) ← Sender
- Email (Email) ← Sender Email
- Received (Date) ← Date
The email body gets saved as page content automatically.
CRM contact capture
If you're using a contacts database:
- Contact (Title) ← Sender
- Email Address (Email) ← Sender Email
- Last Emailed (Date) ← Date
- Notes (Rich Text) ← Subject
Newsletter archive
For saving newsletters:
- Title (Title) ← Subject
- Source (Rich Text) ← Sender
- Date (Date) ← Date
The newsletter body is saved as full page content, preserving headings, links, and formatting.
Tips
- You don't need to map every property. Unmapped properties are left empty (or filled by default values).
- If your Notion database doesn't have the right property types yet, add them in Notion first, then refresh the property list in Quicktion.
- The Title property is required in every Notion database. Mapping it to Subject is the most common choice.
Google Sheets Column Mappings
For Google Sheets destinations, mappings work similarly but with columns instead of Notion properties.
How It Works
Each email field maps to a spreadsheet column. On first save, Quicktion creates column headers automatically. You can then customize which fields are included and their column order in destination settings.
Available Mappings
All the same email fields are available for Sheets destinations:
- Subject — saved as a text column
- Sender — saved as a text column
- Sender Email — saved as a text column
- Date — saved as a date column, formatted to your spreadsheet's timezone
- Body — saved as rich text with clickable links
Attachments
Email attachments are uploaded to a Google Drive folder and linked in a dedicated column. Each attachment gets its own clickable Drive link.
Tips
- You can add or remove columns anytime from destination settings. Changes only affect future emails.
- The email body is saved as rich text, preserving links and basic formatting within the cell.
- If a column is removed from your spreadsheet, Quicktion will skip that field rather than fail.
Airtable Field Mappings
For Airtable destinations, mappings connect email fields to Airtable field types.
How It Works
Each email field maps to a field in your Airtable table. Quicktion reads your table schema and auto-maps email fields to compatible field types. You can customize which fields are included and their mappings in destination settings.
Compatible Airtable Field Types
| Airtable Field Type | Compatible Email Fields |
|---|---|
| Single line text | Subject, Sender, Sender Email |
| Long text | Subject, Sender, Sender Email, Body |
| Rich text | Subject, Sender, Sender Email, Body |
| Sender Email | |
| URL | Sender Email |
| Date | Date |
| Number | (use default values instead) |
| Checkbox | (use default values instead) |
| Single select | Subject, Sender, Sender Email |
| Multi-select | Subject, Sender, Sender Email |
| Attachment | Attachments |
The Body field is best mapped to a long text or rich text field type. The email HTML is converted to markdown, preserving links, headings, and lists.
Attachments
Email attachments are uploaded directly to an Airtable attachment field on the record. Each attachment is accessible from Airtable without any third-party storage.
Tips
- You can add or remove field mappings anytime. Changes only affect future emails.
- If a field is deleted from your Airtable table, Quicktion will skip that mapping rather than fail.
- The Body field works best with long text or rich text fields. Single line text fields will truncate the content.