Track prior authorization requests and chase payer responses with OpenAI and Google Sheets
Ready for 3.0What this workflow does
This AI workflow has 35 nodes and runs on a schedule (cron 0 8 * * *) (plus 2 other triggers). Along the way it connects Google Sheets, Gmail, OpenAI Chat Model and Telegram.
How it runs
Trigger: On a schedule (cron 0 8 * * *) (plus 2 other triggers).
- Read Tracker For Chase (Google Sheets): uses Google Sheets
- Read Tracked PA Requests (Google Sheets): uses Google Sheets
- Normalize PA Request (Edit Fields (Set)): sets 12 fields: pa_id, received_at, patient_ref…
- Find PA Needing Chase (Code): runs custom JavaScript code
- Match Response To Request (Code): runs custom JavaScript code
- Validate PA Request (If): checks a condition and branches into true / false
- AI Write Chase Brief (AI Agent): runs an AI agent, with model: Chase Model
- If: checks a condition and branches into true / false
- AI Review PA Packet (AI Agent): runs an AI agent, with model: Review Model
- Log Rejected Request (Google Sheets): append
…plus 19 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Google Sheets
n8n-nodes-base.googleSheets - Gmail
n8n-nodes-base.gmail - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Code
n8n-nodes-base.code - Telegram
n8n-nodes-base.telegram - Webhook
n8n-nodes-base.webhook - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Prior authorization requests rarely fail loudly. They sit at the payer while the procedure date gets closer. This workflow logs every request as it leaves the clinic, has gpt-6-luna score packet completeness and name the missing documents, chases the payer…