Sign inStart your trial

SalesforceSalesforce
01Integration field card

Salesforce Automation, Approvals & CRM Workflow

Run Salesforce on autopilot. Keep the veto.

217 actions7 triggers

Leads go stale and contacts get deleted before you knew the AI touched them. Rills proposes every Salesforce change; you approve before it ships.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential crm action from Salesforce arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

SALESFORCE · LEAD HYGIENE
82

Update 9 stalled leads to Unqualified and log a closing call?

9 leads · no activity in 21+ days

Same criteria used in last month's cleanup batch

3 leads have open tasks that will also be completed

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Salesforce automation

Salesforce events pile up quietly. A new lead triggers an update sequence, a contact gets reassigned, an opportunity stage shifts, and by the time you look, three things have already happened that you wish you'd reviewed first.

When Salesforce runs unsupervised

The CRM is the record of truth for your whole pipeline, which means a bad automated write goes everywhere. Mistakes don't stay isolated.

  • New lead created fires an update sequence before you've confirmed the lead is even worth pursuing, burning a first-touch impression.
  • Update contact runs against a record mid-deal, overwriting notes your rep added an hour ago.
  • Delete lead removes a contact you might have recognized as a former customer.
  • Associate contact to account links the wrong person to an account, and now every report for that account is off.
  • Complete task marks follow-ups done when the prospect never actually replied.

What Rills does inside Salesforce

Rills sits between the trigger and the write. When a SALESFORCE_NEW_LEAD_TRIGGER or SALESFORCE_NEW_OR_UPDATED_OPPORTUNITY_TRIGGER fires, Rills queues the proposed action, whether that's update lead, log call, or associate contact to account, and holds it until you approve Salesforce changes on your terms.

The lead still gets worked; you just see the proposed action before it touches the record.

When Salesforce events should and shouldn't act on their own

Not every trigger carries the same risk. Some patterns are routine enough to graduate to autonomous; others should always stop for a human read.

  • SALESFORCE_TASK_CREATED_OR_COMPLETED_TRIGGER: Low-stakes logging, safe to graduate once the pattern is consistent.
  • SALESFORCE_ACCOUNT_CREATED_OR_UPDATED_TRIGGER: Routine account hygiene fields can run autonomously; any merge or ownership change should wait for your call.
  • SALESFORCE_CONTACT_UPDATED_TRIGGER: High variance, one update can affect pipeline reporting, active deals, and outbound sequences simultaneously, always needs a review.
  • SALESFORCE_NEW_OR_UPDATED_OPPORTUNITY_TRIGGER: Stage changes tied to revenue; the confidence threshold should stay high before anything acts on its own.
  • SALESFORCE_NEW_LEAD_TRIGGER: First impressions are permanent; proposed actions on net-new leads should clear your approval queue before they go out.
04. Triggers

What wakes Rills up in Salesforce

When these events fire, Rills proposes the next move and waits for your call.

  • webhook

    SALESFORCE NEW CONTACT

    Fires when a new contact is created in Salesforce.

  • webhook

    SALESFORCE NEW LEAD

    Fires when a new lead is created in Salesforce.

  • webhook

    SALESFORCE NEW OR UPDATED OPPORTUNITY

    Fires when an opportunity is created or updated in Salesforce.

  • webhook

    SALESFORCE TASK CREATED OR COMPLETED

    Fires when a task is created in Salesforce or when its status is marked as completed. You can optionally filter by task status or subject line.

05. Actions

What Rills can do in Salesforce

4 of 217 actions across reads, writes, and updates.

  1. 01

    Create contact

    Adds a new contact to your Salesforce CRM with their information such as name, email, and phone number. Use this to build your customer database and keep track of prospects and clients in one centralized location.

  2. 02

    Create lead

    Adds a new prospect to your Salesforce database with essential information like name and company. Use this to capture leads from web forms, email inquiries, or sales conversations and automatically populate them in your CRM.

  3. 03

    Create opportunity

    Creates a new sales opportunity in Salesforce to track potential deals and revenue. Use this to log new customer prospects, project sales, and manage your pipeline in one centralized location.

  4. 04

    Create task

    Create a new task in Salesforce to track activities, follow-ups, and to-dos linked to your contacts, leads, and deals.

06. FAQ

Common questions about Salesforce automation

07. NEXT MOVE

Approve every Salesforce change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.