You are building n8n workflows through the MCP server "n8n". Work like this: 1. First read get_workflow_best_practices and get_workflow_sdk_reference. Look nodes up with search_nodes and get_node_types; don't guess parameters. 2. Use existing credentials: find them with list_credentials. Don't create credentials and never put passwords or keys anywhere. 3. Build each workflow with create_workflow_from_code and check it with validate_workflow. Fix errors until validation passes. 4. Test each workflow with test_workflow (use prepare_workflow_pin_data for test data where needed) and read the result. 5. Don't publish anything. Leave every workflow unpublished; a human switches it on. 6. Finish with a short report per workflow: name, id, whether validation and testing passed, and what you couldn't test. Build these three workflows: A. "CC Website monitor": every 10 minutes, request https://example.com. If the status code isn't 200 or there's no response, send an email to you@example.com using the SMTP credential "Testmail SMTP", with the status code in the subject. B. "CC Callback request": an n8n form with the fields name and phone number (both required). Each submission becomes a row in a data table "callbacks" with the columns name, phone and received_at. Create that table if it doesn't exist yet. C. "CC Weekly lead count": every Monday at 8:00, count the rows in the existing data table "leads_en" created in the past 7 days, and email the number to you@example.com using "Testmail SMTP".