Automation library · Customer support

Answer BigQuery questions in Microsoft Teams with Claude

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 27 steps, 2 branches: large, and worth reading before you trust it with anything live.

Large

Download free
27 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Model 3Logic 17Service 5

The steps in the order they run, from what starts it.

  1. 1When Teams Message ReceivedMicrosoft Teams triggerStarts it
  2. 2On Workflow Error OccurrenceError triggerStarts it
  3. 3Validate Teams MessageCodeLogic
  4. 4Format Error MessageCodeLogic
  5. 5Configure VariablesCodeLogic
  6. 6Send Error Notification to TeamsMicrosoft TeamsService
  7. 7Check Schema Cache ValidityCodeLogic
  8. 8If Cache HitIfLogic
  9. 9Ensure Schema AvailabilityCodeLogic
  10. 10Create Schema Query StatementCodeLogic
  11. 11Build Main Agent Query PromptCodeLogic
  12. 12Fetch Schema from BigQueryGoogle Big QueryService
  13. 13Claude Conversational AgentAnthropicModel
  14. 14Compile Schema Data for LLMCodeLogic
  15. 15Parse Claude Agent OutputCodeLogic
  16. 16If Analytical Intent DetectedIfLogic
  17. 17Build SQL Agent PromptCodeLogic
  18. 18Generate Non-Analytical ResponseCodeLogic
  19. 19Claude SQL Sub-AgentAnthropicModel
  20. 20Share Non-Analytical Reply to TeamsMicrosoft TeamsService
  21. 21Extract and Validate SQL CodeCodeLogic
  22. 22Run BigQuery SQL QueryGoogle Big QueryService
  23. 23Gather SQL Query ResultsCodeLogic
  24. 24Formulate Response PromptCodeLogic
  25. 25Claude Generates ResponseAnthropicModel
  26. 26Create Teams Adaptive CardCodeLogic
  27. 27Send Answer to Teams ChannelMicrosoft TeamsService

How it's built

Starts on
An event in a connected app
Steps
27, with 2 branches
Size
Large: read it before trusting it with anything live
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 27 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 27 steps before you point it at anything that matters.