Send Invoice Email

chargebee.send_invoice_email
ActionCRM & salesconnection required

Calls the Chargebee API with the connection's credentials.

Queue Chargebee's invoice email for the customer. This endpoint is asynchronous only: Chargebee accepts the request and posts the email log to the callback URL later, so the node reports acceptance, not delivery.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Chargebee
Secret shape
the site API key: the raw string, {"api_key": "…"}, or the HTTP Basic pair {"username": "<api key>", "password": ""}
Config it needs
site, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
invoice_id
The Chargebee invoice id.
stringYes———
callback_url
The HTTPS URL Chargebee posts the outcome to when it has finished sending. A Mantle webhook trigger is a natural place to point it.
stringYes—url format—
request_id
The id Chargebee echoes back on the callback so it can be matched to this step. Leave empty to have one generated.
stringNo———

Output

One shape.

result

FieldTypeExample
accepted
True once Chargebee has taken the request; it does not mean the email has been sent.
boolean—
request_id
The chargebee-request-id sent with the call.
string—
callback_url
Where Chargebee will post the email log.
string—
invoice_id
The invoice the email is for.
string—
response
Whatever body Chargebee returned; the documented 202 carries none.
object—
{
  "accepted": false,
  "callback_url": "",
  "invoice_id": "",
  "request_id": "",
  "response": {}
}

Notes

  • The Chargebee site and API key come from the connection; every path below is relative to https://<site>.chargebee.com/api/v2.
  • POST /invoices/{invoice-id}/send_email with Prefer: respond-async
  • Requires Email Engage V2 and a published Send Invoice Email template.

See Send Invoice Email run in a workflow.

In a technical demo we add the Chargebee connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.