> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/flow-studio/nodes.md). # Nodes - [Dapta Phone Call](https://docs.dapta.ai/flow-studio/nodes/dapta-phone-call.md): Connect a Flow Studio automation to a Voice Agent: set the From and To numbers, choose the agent, and pass dynamic variables that personalize the call. - [Get a Record from Hubspot](https://docs.dapta.ai/flow-studio/nodes/get-a-record-from-hubspot.md): Use the Search Record node in Flow Studio to query HubSpot Companies, Contacts or Deals by ID, email or phone, and pick which properties to return. - [Gmail Node](https://docs.dapta.ai/flow-studio/nodes/gmail-node.md): The Gmail node sends automated emails from a Flow Studio flow once you authorize Gmail, then sends a test message in plain text or HTML. - [OpenAI Node](https://docs.dapta.ai/flow-studio/nodes/openai-node.md): Add the OpenAI node to a flow, run it on Dapta AI or your own OpenAI key, pick a GPT model, attach files and choose how the answer comes back. - [Claude Node](https://docs.dapta.ai/flow-studio/nodes/anthropic-node.md): Add the Claude node to a flow, run it on Dapta AI or your own Anthropic key, pick a Claude model, attach files and choose how the answer comes back. - [Google Gemini Node](https://docs.dapta.ai/flow-studio/nodes/google-gemini-node.md): Add the Google Gemini node to a flow, run it on Dapta AI or your own Gemini key, pick a model, attach files and choose how the answer comes back. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dapta.ai/flow-studio/nodes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.