Lesson 5: Build by talking to Claude
Goal: Arjun describes a workflow in plain words; Claude builds it through MCP.
How it works
Section titled “How it works”Auto Appy has an MCP server: a standard socket that AI assistants like Claude can plug into. Claude reads the list of Auto Appy tools (create a workflow, add a step, get the webhook URL, test a step…) and uses them for Arjun, one approved call at a time. New to MCP? What is MCP? explains it in five minutes.
1MCP (Model Context Protocol) is a standard plug that lets AI assistants use apps. Think of USB-C, but for AI.
2Arjun at Skyline Realty asks Claude in plain words: "When a MagicBricks lead comes in, add it to the CRM and WhatsApp the brochure."
3The assistant asks Auto Appy's MCP server what it can do. Auto Appy answers with its list of tools.
4The assistant uses the tools it needs, one at a time: create the workflow, then add the steps. You approve each one.
5Auto Appy does the work and replies. The assistant tells you the workflow is ready to test.
Connect Claude (two minutes)
Section titled “Connect Claude (two minutes)”- In Claude, open Settings → Connectors and choose Add custom connector. Name it
Auto Appy, URLhttps://api.autoappy.com/mcp. - Click Connect. Auto Appy opens; sign in as Arjun.
- On Connect Claude to Auto Appy, tick Read workflows and Build and edit workflows. Leave Run and do things for you off for now. Click Allow access.
- Start a new chat in Claude.
Prefer a token? Settings → MCP connections → Create connection gives one for clients that don’t support sign-in:
Arjun’s conversation
Section titled “Arjun’s conversation”Arjun: When a MagicBricks lead for Skyline Crest comes in, add it to the CRM in the Premium pipeline, assign it to Karan, and WhatsApp the buyer our
crest_welcometemplate.
What Claude does, step by step (each tool call shows in Claude for approval):
autoappy_app_catalogto find the CRM and WhatsApp actions and their fields.autoappy_create_workflowto create a Draft called MagicBricks → Premium.autoappy_get_trigger_setupto get the webhook URL, which Claude gives Arjun to pass to MagicBricks.autoappy_send_test_datawith one realistic sample lead, so later steps can map its fields.autoappy_add_nodetwice (Create lead, Send approved template), thenautoappy_list_mapping_fieldsandautoappy_configure_nodeto fill the fields.autoappy_list_accountsandautoappy_set_accountto attach Skyline’s saved CRM and WhatsApp connections by name.
Claude ends with a link to the new workflow. In the evening, Arjun opens it, tests each step and sets it Live himself.
Good prompts
Section titled “Good prompts”“Build a workflow: when a Facebook lead form lead comes in, create a CRM lead in the Rental pipeline and WhatsApp them rental_welcome. Leave it as a Draft.”
“Explain what the ‘Reply to every property enquiry’ workflow does, step by step, and add a sticky note with your summary.”
“Which of my workflows had failed runs this week? Show the error for each.”
“In ‘Book and remind site visits’, change the reminder from 2 hours to 3 hours before the visit.”
- Connect Claude with read-only permission and ask it to describe each of Skyline’s workflows.
- Ask it to build Lesson 2’s budget split as a new Draft. Compare its result with yours.
- Look at Activity in MCP connections. Which tools did it call?
- MCPA standard plug that lets AI assistants use Auto Appy's tools.
- Connect ClaudeCustom connector, sign in, choose permissions, Allow access.
- MCP toolsEvery tool, and the permission each one needs.
For trainers: how to teach this lesson
- Do it live with the class: let a student dictate the request; you approve each tool call on the projector.
- Talk about trust: what would you let an assistant do on its own, and what always needs a human?
- Compare: building in the editor (Lesson 1) versus by conversation. When is each better?
