Connect Salesforce to Amcards

When something happens in Salesforce, Notis takes the next step in Amcards. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Salesforce to Amcards

View example

Review Amcards contacts after a new Salesforce lead

When Salesforce creates a lead, retrieve Amcards contacts so Notis can check whether the person is already in your mailing contacts and summarize a useful next step.

View example

Review Amcards contacts when a Salesforce account changes

When a Salesforce account is created or updated, retrieve Amcards contacts so Notis can summarize relevant contact context for the account using returned data.

View example

Review Amcards cards after a Salesforce task completes

When a Salesforce task is created or completed, retrieve Amcards cards so Notis can provide a current card inventory alongside the activity report.

View example

Check Amcards after a Salesforce contact update

When an existing Salesforce contact changes, retrieve Amcards contacts so Notis can highlight whether the updated person may already be listed for mailing.

View example

Review Amcards card inventory when an opportunity changes

When a Salesforce opportunity is created or updated, retrieve Amcards cards so Notis can include current card availability in the opportunity report.

View example

Check Amcards contacts for each new Salesforce contact

When Salesforce creates a contact, retrieve Amcards contacts so Notis can summarize possible existing mailing records before follow-up.

View example

Get a scheduled Amcards card inventory digest

On a recurring schedule, retrieve Amcards cards and ask Notis to summarize the current inventory for a lightweight mailing operations check-in.

View example

Request an Amcards contact review by webhook

Start a Notis run with an HTTP request, retrieve Amcards contacts, and summarize the contact details provided with the request against the returned list.

Supported Triggers and Actions

Notis builds workflows that link Salesforce to Amcards. A trigger fires from one place; an action lands in another.

Salesforce triggers

Amcards actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Cards

This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Contacts

This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.

ActionInstant

Account Created or Updated

Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.

TriggerPolling

Contact Updated

Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.

TriggerPolling

Record Updated (Generic SObject)

Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.

TriggerPolling

New Contact Trigger

Triggers when a new Contact is Created in Salesforce.

TriggerPolling

New Lead Trigger

Triggers when a new Lead is created in Salesforce.

TriggerPolling

New or Updated Opportunity

Triggers when a Salesforce Opportunity is created or updated.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.