Integrate Notion page creation into your Mid-call Actions and enable your AI assistant to automatically generate structured documentation, meeting notes, and knowledge base entries in your Notion workspaces during customer conversations.
Token Setup: 1. Fill in integration details 2. Click "Submit" 3. Copy the Internal Integration Token 4. Store the token securely (starts with "secret_")
3
Set Database Permissions
Copy
For each relevant Notion database: 1. Open the database 2. Click "..." → "Add connections" 3. Select the "Famulor Mid-call Actions" integration 4. Click "Confirm"Repeat for: - Customer Database - Meeting Notes Database - Support Tickets Database - Project Documentation Database
4
Collect Database IDs
Copy the database URLs: notion.so/workspace/database_id?v=view_id
During sales call with customer:AI gathers information: - Participants and roles - Discussed topics - Decisions made - Action items with responsibilities - Next steps and timelines
2
Structured Page Creation
Copy
Notion page template:Title: "Sales Meeting: Example Corp - CRM Evaluation (2024-01-15)"Content:"## Participants **Customer:** Max Mustermann (CEO, Example Corp) **Our Team:** Anna Sales (Account Manager) ## Agenda & Discussion - CRM requirements: 500 users, GDPR compliant - Budget discussion: €50k approved for Q1 - Integration needs: Existing ERP system (SAP) ## Decisions ✅ Demo scheduled for next Thursday at 14:00 ✅ Technical deep-dive with IT team required ⏳ Proposal deadline: end of week ## Action Items - [ ] Anna: Compile technical specs (by Wed) - [ ] Max: Coordinate IT team for demo - [ ] Anna: Prepare SAP integration proposal ## Next Steps 1. Demo date: 2024-01-18 14:00 2. Proposal submission: by 2024-01-19 3. Decision expected: end of January"
Template: "Creating a new page '{{title}}' in Notion..."Contextual examples:
Copy
Meeting Notes: "Documenting our conversation in Notion..."Customer Profile: "Creating customer documentation in our knowledge base..."Project Update: "Generating a project update in Notion for the team..."
Success Confirmations
Standard template: "Notion page was created successfully."Enhanced confirmations:
Copy
With team context: "Documentation created and the team has access."With linking: "Meeting notes are available in Notion – your team has been notified."With follow-up: "Customer profile was created in our knowledge base. The account team can reference it for future calls."
Bidirectional sync pattern:1. Mid-call Action creates Notion page2. Notion page URL is added as a note on the HubSpot contact3. HubSpot updates trigger Notion page updates4. Notion comments are logged as HubSpot activitiesImplementation: - Notion database with HubSpot contact ID property - Webhook integration for bidirectional updates - Conflict resolution for simultaneous changes
Asana-Notion Integration
Copy
Task documentation workflow:1. create_asana_task for action items2. create_notion_page for detailed documentation3. Asana task links to Notion page4. Notion page references Asana task IDCross-platform benefits: - Asana: task tracking and deadlines - Notion: rich documentation and context - Team: full transparency and traceability
Cause: Incorrect database ID or integration lacks permissionNotion error: "object": "error", "status": 404, "code": "object_not_found", "message": "Could not find database"Fallback: "Documentation could not be created in the specified database. Creating alternative documentation instead."Resolution: - Validate database ID - Check integration permissions - Fallback to default database
Invalid Properties (400)
Copy
Common property errors: - Select value not in database options - Invalid date format - Missing required properties - Property type mismatchGraceful handling: - Use property defaults - Store invalid values as rich text - Still create page (with warnings)Error recovery: "Documentation was created with default values. Team can manually adjust details."
Rate Limiting (429)
Copy
Notion limits: - 3 requests per second - Burst capacity: 10 requests - Content limits: 100 blocks per requestRetry strategy: - Jitter-based backoff - Content splitting for large pages - Priority queue for critical documentationUser experience: "Documentation is being created – extensive content may take a moment."
Database Schema: Ensure your Notion database properties match the parameter schema definitions. Changes to the database schema require updates to the tool configuration.
Collaboration Tip: Use Notion comments and @-mentions in automatically created pages to encourage team discussions and coordinate follow-up actions.