ceven

Amcards

Sends physical greeting cards to your customers based on CRM triggers and manages your contact lists for automated direct mail campaigns.

Try Amcards in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Amcards integration

    • Describe the outcome and Ceven picks the right Amcards calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Amcards data, across all 10 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Amcards access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Amcards, when, and on whose behalf.
    • The agent pauses and asks when Amcards is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Amcards.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Amcards action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Amcards, and when to use it.

Get cards
Pull a list of all available card templates associated with the account to choose the right design for a campaign.
Get contacts
Retrieve a list of contacts using filters like name or email to verify a recipient exists before sending.
Create contact
Add a new recipient to Amcards. Use this when a new lead or customer is created in your primary CRM.
Update contact
Refresh contact details like mailing addresses or names to ensure physical cards reach the correct destination.
Send card
Trigger the printing and mailing of a specific card to a contact. Include the custom message and template ID.
Delete contact
Remove a contact from the Amcards list. Use this for data cleanup or when a customer requests removal.
Search contacts
Query the contact database by specific attributes to find a recipient without knowing their unique ID.
List campaigns
Pull all active or past mailing campaigns to analyze reach and frequency of physical touch points.
Get card details
Pull specific metadata for a single card template including pricing and available personalization fields.
Create campaign
Set up a new batch mailing project for a specific group of contacts and a chosen card design.
Update campaign
Modify the details or the recipient list of an existing mailing campaign before it is finalized.
Get account balance
Check the remaining credit or card balance to ensure there are enough funds for an automated send.

12 actions · scroll to see them all

Frequently asked questions

Ceven relies on the data provided in your connected CRM or database. When the agent triggers a send action through Amcards, it passes the address exactly as it appears in your records. Amcards performs its own internal validation during the printing process. If an address is flagged as undeliverable by the postal service, Amcards typically handles the return process. To minimize errors, we recommend running a data cleaning workflow in Ceven to standardize addresses before they are pushed to the Amcards contact list, ensuring that your physical mail budget is not wasted on invalid destinations.
Yes. The agent can dynamically generate the message body for every single card. You can instruct the agent to pull specific details from your CRM, such as the customer name, the date of their last purchase, or a specific project milestone. The agent then maps this generated text into the message field of the Amcards send request. This allows you to scale physical mail without losing the personal touch, as each recipient receives a card that mentions their specific achievements or interactions with your business instead of a generic template.
If your Amcards account has insufficient credits, the API will return an error when Ceven attempts to trigger a send. The Ceven agent is designed to catch these errors and can be configured to alert you via Slack or email immediately. You can set up a specific monitoring workflow that uses the get account balance action to check your credits every Monday morning. This ensures you can top up your account before your automated anniversary or birthday workflows fail to deliver cards to your most important customers.
Amcards has specific regional availability for its physical printing and mailing services. While Ceven can send the data for any address to the API, the actual delivery depends on the Amcards service area. If you attempt to send a card to a country not supported by Amcards, the API will return a validation error. We suggest creating a workflow that filters your contact list by country before calling the send action. This prevents the agent from attempting to process unsupported addresses and keeps your workflow logs clean of predictable delivery failures.
Amcards imposes rate limits on their API to ensure system stability. If you attempt to send thousands of cards in a single burst, you may encounter a 429 too many requests error. Ceven manages this by implementing an intelligent queue for large campaigns. Instead of firing all requests simultaneously, the agent spaces out the calls to stay within the Amcards API thresholds. This means your large scale customer appreciation campaigns will still process fully, though they may take a few hours to transition from the queue to the printing house.
Once the agent calls the send card action and Amcards accepts the request, the process moves quickly to the printing stage. Because these are physical products, there is a very short window for modifications. If you realize a mistake was made, you must act immediately within the Amcards dashboard. Ceven cannot recall a card once the API has confirmed the order is in production. We recommend setting up an approval step in your Ceven workflow for high value clients, where the agent drafts the message and waits for your sign off.
Ceven acts as the orchestrator between your source of truth and Amcards. You can set up a real time sync where every new contact added to your CRM is automatically created as a contact in Amcards. Alternatively, you can run a daily batch sync that updates addresses and names. The agent uses the email address as the primary key to prevent duplicate records. If a contact already exists, the agent uses the update contact action to ensure the mailing address is current, which is critical for physical mail automation.
Yes, this is a core strength of the Ceven integration. You can build logic into your workflow that checks a customer field, such as account value or tier. For example, you can instruct the agent to use a premium foil card template for your platinum clients and a standard card for others. The agent simply maps the corresponding template ID from your Amcards account to the send request based on the logic you define. This allows you to differentiate your customer appreciation strategy based on the actual value of the relationship.

Alternatives to Amcards

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Postable logoPostableHandwrytten logoHandwryttenLob logoLob

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Amcards and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free