CardClan
for LuumenAI

CardClan helps teams personalize and send digital cards, generate card links, and manage card integration workflows.

Bring CardClan into the same conversation as the systems behind it. LuumenAI reads campaigns, audiences, and delivery status for context, and changes them only through previewed, approved, audited actions.

The CardClan toolbox

9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Card DetailsGet a CardClan card's title, merge-tag requirements, and owning workspace details by card ID.
  • ReadGet Integration ConfigurationGet a CardClan integration configuration by either integration ID or card ID.
  • ReadList CardsList cards in a CardClan workspace, including card IDs needed for details, integration configuration, personalized links, and sending.
  • ReadList Email AccountsList configured CardClan sender accounts that can be selected when sending a card.
  • ReadList Workflow CardsList cards with active CardClan integration workflows and return their integration, card, and workspace IDs.
  • ReadList WorkspacesList CardClan workspaces accessible to the connected account, including the workspace IDs needed to find cards and create integration configurations.
  • WriteCreate Integration ConfigurationCreate a persistent CardClan integration configuration linking a card to its workspace. Approval by default
  • WriteGenerate Personalized Card URLGenerate a personalized CardClan viewing URL without sending an email. Approval by default
  • WriteSend CardImmediately personalize and send a CardClan card by email to one or more recipients. Approval by default

Questions

How does LuumenAI connect to CardClan?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in CardClan on its own?

Read actions answer immediately. Anything that writes — create integration configuration, generate personalized card url, send card — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to CardClan — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put CardClan to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.