How to Automate CRM Updates with IFTTT

IFTTT has no HubSpot or Salesforce app, so CRM updates run through Webhooks. Here are IFTTT's own steps for both directions, plus timing and limits.

By Galactic News Editorial · Published 2026-11-07T19:31:53+00:00 · Updated 2026-11-07T19:31:53+00:00

Automate CRM updates with IFTTT Webhooks Applets

How to Automate CRM Updates with IFTTT

IFTTT connects more than 1,000 services through simple rules called Applets. One event triggers one or more actions. But IFTTT has no built-in HubSpot or Salesforce service. So CRM updates have to travel through its Webhooks service instead. A CRM event sends a web request into IFTTT. Or an IFTTT event sends a web request out to your CRM. This guide uses IFTTT's own help documentation for every step.

First, check what IFTTT can connect to

IFTTT's catalog leans toward consumer apps and smart devices. Independent checks of IFTTT's own service list found no HubSpot and no Salesforce. That absence shapes the whole approach. You cannot pick your CRM from a menu inside IFTTT. Instead, you bridge the gap with Webhooks. Webhooks let applications talk by sending HTTP requests. IFTTT's Webhooks service supports triggers, queries, and actions. If your CRM or an adjoining tool can send or receive a web request, the bridge works.

How to automate CRM updates with IFTTT using Webhooks

The most common pattern sends CRM changes into IFTTT. IFTTT then logs or announces each update in tools it does support. Follow these steps from IFTTT's help center:

  1. Connect the Webhooks service. Visit the Webhooks service page in IFTTT and connect it to your account. IFTTT generates your personal Webhooks key.
  2. Create a new Applet. Click Create to start building.
  3. Add the trigger. Click Add next to If This. Search for Webhooks. Select Receive a web request, or Receive a web request with a JSON payload.
  4. Name the event. Enter an event name such as crm_update. You will use this exact name when sending the request.
  5. Add the action. Click Add next to Then That. Choose the service and action you want, such as adding a row to a tracking spreadsheet or sending a notification.
  6. Copy your webhook URL. Open the finished Applet and scroll to Your webhook URL. It follows the format maker.ifttt.com/trigger/{event}/with/key/{webhooks_key}. The JSON version inserts /json/ before /with/key/.
  7. Connect your CRM side. Paste the URL into the webhook or automation setting of the tool that detects the CRM change. When the event fires, that tool calls the URL and your Applet runs.
  8. Test it. Make a small CRM change and confirm the action happens. For the simple trigger, you can pass up to three values with the request. The JSON trigger accepts a JSON body instead.

The reverse pattern: push updates into your CRM

You can also send data the other way. An event in a service IFTTT supports becomes the trigger. The Webhooks action then sends an HTTP request to an endpoint you control. Build it like this:

  1. Create an Applet and choose your trigger service and trigger.
  2. For Then That, search for Webhooks and select Make a web request.
  3. Paste the inbound webhook URL your CRM or middleware provides.
  4. Set the method, usually POST, and the content type, usually application/json.
  5. Build the body with the fields your endpoint expects. Add values from the trigger using ingredients.
  6. Save the Applet and run a test event. Confirm the record changed inside your CRM.

Keep your Webhooks key private. IFTTT warns that anyone with your key may trigger your Applets.

Timing: polling versus realtime

Not all Applets fire instantly. Webhooks triggers are realtime. IFTTT says Webhook Applets normally run within a few seconds. Other triggers rely on polling. IFTTT checks the trigger service on a cycle instead. Polling checks happen every hour on the Free plan. They happen every five minutes for Pro and Pro+ users. Pick the Webhooks route when update timing matters.

If an Applet does not fire

  1. Open the Applet and check its Activity for errors.
  2. Confirm the event name in your request matches the Applet exactly.
  3. Confirm the URL uses your current Webhooks key.
  4. If it still fails, regenerate the key. Go to the Webhooks settings page and click Regenerate key. Then update the URL everywhere you pasted it.
  5. Remember that outgoing web requests may be rate limited.

Limits to know before you start