km-meeting-upload

Yes, you can ingest Google Drive links to generate Odoo meeting minutes. The workflow transcribes the linked audio via NotebookLM and then guides you through a LINE conversation to gather project, location, and attendee data before writing to Odoo.

Binding LINE users to Odoo requires LINE OAuth user binding and mapping the res.users oauth_uid. This ensures the system authenticates the user before creating the job.meeting.minutes record through the Odoo MCP integration.

The system handles missing data by running a multi-turn LINE dialogue to collect required fields like project, location, and attendees. It only writes the meeting minutes to Odoo after this guided conversation gathers the necessary information.

The workflow fails for unbound users because it requires LINE OAuth binding and an accurate res.users oauth_uid mapping. Error handling returns friendly messages when it cannot identify the Odoo user to associate with the job.meeting.minutes record.

You can prevent duplicate meeting minutes because the workflow includes error handling for duplicate km_source_ref records. It preserves draft states and returns friendly messages if it detects that a specific audio source has already been processed.