<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: VeyCall</title>
    <description>The latest articles on DEV Community by VeyCall (@veycallai).</description>
    <link>https://dev.to/veycallai</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4240039%2F17ea4a5f-4a30-4ce2-b13f-e9d6f6941787.png</url>
      <title>DEV Community: VeyCall</title>
      <link>https://dev.to/veycallai</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/veycallai"/>
    <language>en</language>
    <item>
      <title>Send your VeyCall leads to Google Sheets, your CRM or Slack with Make, Zapier or n8n</title>
      <dc:creator>VeyCall</dc:creator>
      <pubDate>Wed, 18 Nov 2026 14:00:05 +0000</pubDate>
      <link>https://dev.to/veycallai/send-your-veycall-leads-to-google-sheets-your-crm-or-slack-with-make-zapier-or-n8n-3pn3</link>
      <guid>https://dev.to/veycallai/send-your-veycall-leads-to-google-sheets-your-crm-or-slack-with-make-zapier-or-n8n-3pn3</guid>
      <description>&lt;p&gt;Your voice agent talks to visitors day and night, and every lead shows up in your VeyCall dashboard. But your team probably lives somewhere else: a shared Google Sheet, a CRM like HubSpot or Pipedrive, a Slack channel. With webhooks, each new lead goes there by itself, a few seconds after the conversation ends.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;A webhook is an address that receives events. VeyCall sends one each time something happens: a new lead, a lead that changes, or a conversation that ends, with its transcript. Automation tools like Make, Zapier and n8n give you that address, then do whatever you ask with the data.&lt;/p&gt;

&lt;p&gt;Setup takes three steps, whatever the tool:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create the trigger: &lt;strong&gt;Webhooks › Custom webhook&lt;/strong&gt; in Make, &lt;strong&gt;Webhooks by Zapier › Catch Hook&lt;/strong&gt; in Zapier, or a &lt;strong&gt;Webhook&lt;/strong&gt; node in n8n. Copy its address.&lt;/li&gt;
&lt;li&gt;In VeyCall, open &lt;strong&gt;Integrations › Webhooks&lt;/strong&gt;, click &lt;strong&gt;Add a webhook&lt;/strong&gt;, paste the address and tick &lt;strong&gt;New lead&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;Send test&lt;/strong&gt;. Your tool receives a sample lead with every field (name, phone, email, request, priority, link), so you can map them in the next step.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Recipe 1: every lead in a Google Sheet
&lt;/h2&gt;

&lt;p&gt;The simplest and most popular. Create a sheet with the columns Date, Name, Phone, Email, Request, Priority and Link. After the webhook trigger, add &lt;strong&gt;Google Sheets › Add a row&lt;/strong&gt; (Make) or &lt;strong&gt;Create Spreadsheet Row&lt;/strong&gt; (Zapier), and map:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Date: &lt;code&gt;data.created_at&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Name, Phone, Email: &lt;code&gt;data.name&lt;/code&gt;, &lt;code&gt;data.phone&lt;/code&gt;, &lt;code&gt;data.email&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Request: &lt;code&gt;data.notes&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Priority: &lt;code&gt;data.priority&lt;/code&gt; (normal or urgent)&lt;/li&gt;
&lt;li&gt;Link: &lt;code&gt;data.url&lt;/code&gt;, which opens the lead in VeyCall&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Your whole team sees new leads without logging in anywhere, and you keep a history you can filter and share.&lt;/p&gt;

&lt;h2&gt;
  
  
  Recipe 2: urgent leads in Slack, right away
&lt;/h2&gt;

&lt;p&gt;When a customer describes a leak, pain or a same-day need, VeyCall marks the lead urgent. Add a filter after the trigger (&lt;code&gt;data.priority&lt;/code&gt; equals &lt;code&gt;urgent&lt;/code&gt;), then a &lt;strong&gt;Slack › Send a message&lt;/strong&gt; step: "Urgent lead: {name}, {phone}: {notes}". Whoever is free calls back.&lt;/p&gt;

&lt;h2&gt;
  
  
  Recipe 3: a contact in your CRM
&lt;/h2&gt;

&lt;p&gt;Add a &lt;strong&gt;HubSpot › Create a contact&lt;/strong&gt; or &lt;strong&gt;Pipedrive › Create a person&lt;/strong&gt; step, mapping the name, email and phone. Use &lt;code&gt;data.notes&lt;/code&gt; as the first note or the deal name. If you also tick &lt;strong&gt;Lead updated&lt;/strong&gt; in VeyCall, you can keep the status in sync when your team marks a lead as contacted or won.&lt;/p&gt;

&lt;h2&gt;
  
  
  Good to know
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Leads from missed calls on your &lt;a href="https://veycall.com/blog/missed-calls-to-leads-onoff" rel="noopener noreferrer"&gt;Onoff Business line&lt;/a&gt; are sent too, with the voicemail transcript.&lt;/li&gt;
&lt;li&gt;If your tool is briefly down, VeyCall retries several times over about two hours.&lt;/li&gt;
&lt;li&gt;Every delivery is signed, so a developer can check it really comes from VeyCall. The details are in the &lt;a href="https://veycall.com/docs#webhooks" rel="noopener noreferrer"&gt;documentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Webhooks are a &lt;a href="https://veycall.com/pricing" rel="noopener noreferrer"&gt;one-time activation ($49)&lt;/a&gt;. Calendar booking is available with &lt;a href="https://veycall.com/docs#booking" rel="noopener noreferrer"&gt;Cal.com&lt;/a&gt;, and native CRM connections are on the way; until then, these recipes cover most needs in a few minutes.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://veycall.com/blog/send-leads-to-google-sheets-crm" rel="noopener noreferrer"&gt;veycall.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>nocode</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
