Gmail Music Cue Sheet Clearance Workflow (n8n + OpenAI)

Clear music rights from cue-sheet emails—automatically

The Gmail Music Cue Sheet Clearance Workflow (n8n + OpenAI) monitors your inbox for cue-sheet and music clearance emails, extracts structured rights data with OpenAI, cross-checks it against internal rights APIs, and prepares a supervisor approval clearance packet. Approved records are committed to production; gaps are routed for follow-up—while evidence is archived to Google Drive and logged in Google Sheets.

What this workflow does

• Monitors Gmail every minute for emails whose subjects contain “cue sheet” or “music clearance” and that include at least one attachment.
• Normalizes cue text by combining the email body into a single cue field.
• Extracts cue + rights metadata using OpenAI (e.g., production, cues, territories, media, and term).
• Verifies against internal evidence by calling two HTTP APIs: matching PRO work registrations and master ownership claims.
• Calculates clearance gaps (e.g., missing writer share totals, missing master owner, or missing sync quote) and assigns a risk status.
• Generates a supervisor-ready packet as rights clearance JSON (preserving any gaps) and emails it via Gmail for approval.
• Routes outcomes after webhook approval:
  • Approved: commits clearance via an HTTP API.
  • Gaps: emails the gap list to a rights coordinator for follow-up.
• Archives evidence by saving the final clearance evidence JSON to Google Drive and appending packet details to an “Audit Log” tab in Google Sheets.

Use cases

• Rights teams processing daily cue-sheet submissions without manual copying and checking.
• Automation engineers building a Gmail-to-approval workflow for music clearance workflows.
• SaaS operators who need audit-ready evidence trails for approvals, commits, and gap resolution.

Technical details

• n8n nodes include if, set, code, wait, gmail, and merge.
• Uses OpenAI for structured extraction and packet JSON drafting.
• Calls two HTTP APIs to fetch PRO work registrations and master ownership claims.
• Requires Gmail OAuth2 setup and configuration of recipient(s).