Make: Your AI Replies Go Out Without a Signature. Fetch the Real One From Signatoro With an HTTP Module
Disclosure: Signatoro's founder, Katya Rozenoer, tested this scenario end to end and shared the blueprint I use in the lesson. I'm not paid by Signatoro and there's no affiliate link. Signatoro is an email signature platform, not an e-signature (document signing) tool, so if you came here for contract signing, this isn't that. Here's a problem I didn't expect when I first added AI to a Make.com…
In a scenario using Make.com, an AI response generated by ChatGPT for a dental practice, Brookside Dental, was found to be unsigned, appearing as a form letter. The issue arose because the Gmail module, which is used to send the replies, only adds a signature if the email is composed in the Gmail web interface. To address this, Signatoro, an email signature platform, was integrated into the scenario.
The solution involves saving the signature details on Signatoro, including the name, title, company, phone number, email, and website. An API key is then generated for use in the Make.com scenario. This key is used to fetch the signature from Signatoro via an HTTP module. The signature is then appended to the response generated by ChatGPT in the Gmail module, ensuring that every reply carries the correct, current signature.
This approach is particularly useful for small teams, front desks, and office managers who use Make.com to respond to form requests and wish to maintain consistency in their professional signatures. The key points to note in the implementation include saving the signature on Signatoro, generating an API key, setting up the HTTP module to fetch the signature, and configuring the Gmail module to include both the AI-generated text and the fetched signature in the emailed reply.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
