Gmail carries the messages a team sends and receives, and Google Docs is where longer-form writing lives. In NoClick you can connect them so email content becomes document text, or a doc gets emailed out. The Gmail node sends emails, creates drafts, and reads messages from the inbox, while the Google Docs node creates documents and appends, inserts, or replaces text.
Yes. Use the Gmail read-emails operation to pull messages from the inbox, then use the Google Docs append-text operation to add each message to a document, building a searchable archive.
Use the Google Docs fetch-document operation with content included, then pass the text into the Gmail send-email operation as the body. The Gmail node supports HTML bodies if you want formatting.
Yes. The Gmail create-draft operation makes an unsent draft, which is useful when you want a person to review the doc-based content before it goes out.
They can. Both Gmail and Google Docs authenticate with Google OAuth, so you can connect the same account once and use it for both nodes in the workflow.
Yes. The Gmail node has a trigger that polls for new emails on a schedule. When one matches your criteria, the workflow can immediately write it into a Google Doc.