How It Works
Safina does not connect to Notion directly. Instead, it uses webhooks to send structured call data to an automation platform (Zapier, Make, or n8n) which then creates entries in your Notion database via the Notion API.
The data flow:
Safina (call ends) -> Webhook (JSON payload) -> Zapier / Make / n8n (automation) -> Notion API (database entry)
This approach is flexible. You control exactly which Notion database receives the data, which fields get populated, and what additional logic runs in between (filtering, formatting, notifications).
Setup via Zapier (5 Steps)
1. Create a Notion Database
In Notion, create a database with the fields you want to track: Name, Phone, Date, Summary, Urgency, Action Items, Status. Use a full-page database for the best experience.
2. Create a Zap in Zapier
Log in to Zapier and create a new Zap. Choose “Webhooks by Zapier” as the trigger and select “Catch Hook.” Zapier generates a unique webhook URL.
3. Add the Webhook URL in Safina
Open the Safina app, go to Settings > Integrations > Webhooks. Add a new webhook with the Zapier URL. Select the call.ended event as the trigger. This ensures the webhook fires after each call, when the full summary is available.
4. Map Fields to Notion
Back in Zapier, choose Notion as the action app and select “Create Database Item.” Connect your Notion account and select your database. Map the Safina webhook fields to your Notion database columns:
| Safina Webhook Field | Notion Database Column |
|---|---|
caller.name | Name |
caller.phone | Phone |
timestamp | Date |
summary | Summary |
urgency | Urgency |
action_items | Action Items |
call.duration_seconds | Duration |
5. Test and Activate
Click “Test” in Zapier. Safina sends a test payload. Verify that a new entry appears in your Notion database with the correct data. Activate the Zap.
Done. Every call now creates a Notion database entry automatically.
What Gets Saved in Notion
Each call generates a structured database entry with the following information:
- Caller name as stated during the call
- Phone number from caller ID or stated during the call
- Date and time when the call occurred
- Duration how long the call lasted
- Summary 2-3 sentence overview of the caller’s request
- Urgency high, medium, or low
- Action items specific next steps extracted from the conversation
- Transcript full conversation text (optional, depending on your webhook configuration)
- Callback requested whether the caller wants a callback and preferred time
Suggested Notion Database Template
Set up your Notion database with these properties for the best workflow:
| Property | Type | Purpose |
|---|---|---|
| Name | Title | Caller name |
| Phone | Phone | Callback number |
| Date | Date | Call timestamp |
| Summary | Text | Call overview |
| Urgency | Select (High/Medium/Low) | Prioritization |
| Action Items | Text | Next steps |
| Status | Select (New/In Progress/Done) | Your follow-up tracking |
| Assigned To | Person | Team member responsible |
| Duration | Number | Call length in seconds |
Add a “Board” view grouped by Status for a kanban-style workflow. Add a “Calendar” view to see calls by date. Filter by Urgency to focus on high-priority items first.
Use Cases
Freelancer Call Log
You are a freelancer juggling multiple clients. Every call goes into your Notion call log with the client name, request, and action items. At the end of the week, you review the database, check off completed items, and invoice accordingly. No call slips through the cracks.
Property Management Tenant Requests
Tenants call about maintenance issues, lease questions, and complaints. Each inquiry lands in a Notion database with the property address, issue type, and urgency. Property managers review the list, assign tasks, and track resolution status. The database becomes your maintenance pipeline.
Project Management
Your team uses Notion as a project hub. Client calls about ongoing projects get logged with the project name and requested changes. Link call entries to project pages in Notion for a complete audit trail. No information lives only in someone’s memory.
Alternative: Setup via Make or n8n
If you prefer Make or n8n over Zapier, the process is similar:
Make: Create a scenario with a Webhooks trigger module. Add a Notion module (“Create a Database Item”). Map the fields. Activate.
n8n: Create a workflow with a Webhook node. Add a Notion node (“Create Database Page”). Map the fields. Activate. n8n can be self-hosted for full data control.
All three platforms support the same webhook payload from Safina. Choose the one your team already uses.
Frequently Asked Questions
Why is there no direct Notion integration?
Notion’s API is designed for structured data operations rather than real-time event processing. By using webhooks with an automation platform, you get more flexibility: you can filter calls, format data, add logic, and connect multiple destinations in a single workflow. The webhook approach also means Safina works with any tool that has a Notion integration, not just one proprietary connector.
How quickly does a call appear in Notion?
Typically within 10-30 seconds after the call ends. The webhook fires immediately when the call summary is ready. The automation platform processes it in seconds. Notion’s API creates the entry almost instantly.
Can I update existing Notion entries instead of creating new ones?
Yes, with some configuration in your automation platform. For example, in Zapier you can use a “Find or Create Database Item” action to check if a caller already has an entry (by phone number) and update it instead of creating a duplicate. This is useful for repeat callers.
Does this work with Notion’s free plan?
Yes. Notion’s free plan supports databases and API access. The integration works without a paid Notion subscription. If your team has more than 10 members or needs advanced permissions, you may need Notion’s paid plan for those features, but the Safina integration itself works on free.