/tools/optimized · daily

One expert hack per tool, every morning.

Deep tool craft, signature prompts, multi-tool workflows, integrations — plus the AIO / SEO / GEO moves that make your stack legible to answer engines. Tactical, installable today, written for the AI Health Stack.

Get the Atlas — €5 Tools hub

Integration · today2026-05-22· Tool: Zapier (Agents)

7 ways to use Zapier (Agents) to streamline your operational processes

Streamline your operational processes with these 7 Zapier (Agents) integrations, ensuring data flows effortlessly across your existing tools.

Manual data transfer, missed follow-ups, and disconnected systems can create unnecessary friction when focusing on client well-being. This can lead to fragmented client records and reduced time for actual care. By leveraging Zapier (Agents) to connect your existing tools, you can automate these routine tasks and create a more cohesive workflow.

Automate Wearable Data to Notion: Set up a Zap that triggers when new data is exported from your wearable app (e.g., Apple Health via a CSV export to a cloud folder). Have Zapier parse the CSV and automatically append new entries to a "Daily Metrics" database in Notion, populating fields like `Date`, `Steps`, `Sleep (hours)`, and `Heart Rate Avg`.
Client Intake Form to CRM: Create a Zap to instantly transfer new client intake form submissions (from tools like Typeform or Google Forms) to your CRM system (e.g., HubSpot, Airtable). Map form fields directly to corresponding CRM fields like `Client Name`, `Email`, `Phone`, and `Initial Concern`.
Calendar Event Logging for Billing: Configure a Zap to detect new events on your calendar (e.g., Google Calendar, Outlook Calendar) with specific keywords like "Client Session." This Zap can then create a detailed log in a Google Sheet for billing purposes, including `Client Name`, `Date`, `Duration`, and `Service Type`.
Meeting Notes & Follow-up Tasks: Use a Zapier Agent to listen for new entries in a shared meeting notes document (e.g., a specific folder in Google Docs or Dropbox Paper). The Agent can then extract action items and automatically create tasks in your project management tool (e.g., Asana, Trello) assigned to relevant team members, including a due date.
Automated Welcome Email Sequence: When a new client is added to your CRM system, trigger a Zap to initiate a personalized welcome email sequence through your email marketing platform (e.g., Mailchimp, ConvertKit). This ensures new clients receive essential information and onboarding resources promptly.
Lab PDF to Data Extraction: Set up a Zap that watches a designated cloud storage folder (e.g., Dropbox, Google Drive) for new PDF lab results. The Zap can then use optical character recognition (OCR) capabilities (provided by Zapier integrations like PDF.co) to extract key data points (e.g., `Glucose levels`, `Cholesterol HDL`, `Cholesterol LDL`) and push them into a client-specific ledger in a spreadsheet or database.
Appointment Reminders & Pre-session Forms: Create a Zap that triggers X hours before a scheduled appointment in your calendar. This Zap can automatically send a reminder email or SMS to the client, including a link to any pre-session forms or questionnaires that need to be completed before their appointment.

These integrations strengthen your personal and practice Ledgers by ensuring seamless data flow.

Read the full deep-dive →Get the workflow template →

Previous hacks

GEO2026-05-21· Cognition (Devin)
6 ways to use Cognition (Devin) to generate API documentation for your AI Health Stack
Discover 6 efficient ways to leverage Cognition (Devin) for automatically generating API documentation, streamlining your AI Health Stack’s maintainability and discoverability.
Show the hack
Your AI Health Stack relies on interconnected tools, often with bespoke APIs. Manually documenting these endpoints can be a time-consuming bottleneck, creating friction for new integrations or even for yourself when revisiting older projects. This hack focuses on using Cognition (Devin) to automate the API documentation process, ensuring your internal tools are always well-documented and easily understandable.
1. Swagger/OpenAPI Generation: Hand Cognition (Devin) a codebase and a prompt like "Generate OpenAPI 3.0 YAML for all API endpoints in this repository." Specify the output format and location (e.g., `docs/openapi.yaml`).
2. Linting and Validation: After initial generation, ask Cognition (Devin) to "Validate `openapi.yaml` against the OpenAPI specification and suggest corrections." This ensures compliance and consistency, preventing common errors.
3. Client Library Scaffolding: For practitioners integrating external tools, prompt Cognition (Devin) with "Generate a Python client library from `openapi.yaml` for interacting with the `MyHealthAPI` service." This provides immediate functional code.
4. Endpoint Summary Table: Instruct Cognition (Devin) to "Create a markdown table summarizing all API endpoints, their methods, and a brief description, from `docs/openapi.yaml`." This provides a quick overview for internal and external consumers.
5. Automated Doc-string Insertion: Provide Cognition (Devin) with existing code and ask it to "Parse this Python code and insert Google-style docstrings for all functions, referencing `openapi.yaml` for endpoint details." This integrates documentation directly into the source.
6. Version Control Integration: Configure Cognition (Devin) to automatically trigger documentation regeneration and commit changes to a `docs/` branch in your Git repository whenever API-related files are updated, using a pre-commit hook or CI/CD pipeline.
This hack streamlines your Protocol maintenance.
Deep-dive →Template →
SEO2026-05-20· Lovable
SEO Hack: Dynamic FAQ Schema with AI
Improve search visibility and user engagement for your wellness AI content by generating dynamic FAQ schema.
Show the hack
For wellness practitioners, leveraging structured data is critical for search engine optimization. Your AI-powered applications, especially those built with tools like Lovable for custom intake portals or information hubs, can benefit significantly from dynamic FAQ schema. This not only clarifies content for search engines but also directly answers user queries, increasing click-through rates.

Traditionally, manually adding FAQ schema is time-consuming. However, by integrating a simple AI prompt, you can generate this schema automatically, ensuring your content is always fresh and discoverable. This approach helps search engines understand the context of your wellness services and provides direct answers within search results, making your offering more attractive to potential clients.

Here’s how to implement this:
1. Identify Core Questions: Review existing client inquiries or anticipated questions related to your AI health stack and services. Compile a list of 5-10 common questions.
2. Formulate an AI Prompt: Use a prompt like: "Generate FAQPage schema JSON-LD for the following questions and answers about [Your Wellness Service/AI App]: [Question 1]? [Answer 1]. [Question 2]? [Answer 2]."
3. Generate and Implement: Feed your questions and answers into your AI tool to produce the JSON-LD. Copy this output.
4. Embed in Your Application: Integrate the generated JSON-LD within the `<head>` or `<body>` section of the relevant pages in your wellness application (e.g., your Lovable-built intake portal landing page).
Deep-dive →Template →

Personalised

More daily tool hacks for your stack

Based on what you've been reading — always learning.

See all →

Keep exploring the stack.

Three doors into the rest of Wellness & AI — pick the one that matches where you are.

Free · Live

Build it live in 45 min

Bi-weekly Zoom workshop with Sabin. Build your AI Health Stack end-to-end, ask one real question, leave with a working setup.

Reserve a seat

Learn the method

The 3-Layer Course

Build your own AI Health Stack in 4 weeks. Same method we use with private clients — Research, Ledger, Protocol.

See the courses

The list

The AI Health Stack

Every AI tool I actually use for personal health, one line each. Click any tool for a free deep-dive.

See the stack