Send handwritten notes from n8n workflows

If n8n can see the event, it can send a card. One HTTP Request node calls the notecardHQ API.

The HTTP Request node

  • Method: POST. URL: https://you.notecardhq.com/api/v1/notes.
  • Authentication: Generic credential, Header Auth, name Authorization, value Bearer YOUR_API_KEY. Keeping the key in a credential keeps it out of the workflow JSON.
  • Send Headers: Idempotency-Key = an expression unique to the event, for example {{ 'order:' + $json.id }}.
  • Send Body: JSON, using expressions for the fields:
{
  "externalId": "{{ $json.customer_id }}",
  "recipient": {
    "firstName": "{{ $json.first_name }}",
    "lastName": "{{ $json.last_name }}",
    "address1": "{{ $json.address1 }}",
    "city": "{{ $json.city }}",
    "state": "{{ $json.state }}",
    "postalCode": "{{ $json.zip }}",
    "country": "{{ $json.country_code }}"
  },
  "content": "Hi {{ $json.first_name }},\n\nThank you for being a customer.\n\nThe team"
}

Retries

Turn on Retry On Fail for the node. Because every retry carries the same Idempotency-Key, a retried request returns the original note instead of mailing a second card. Errors in the 400s (a bad field, an undeliverable US address) will not succeed on retry, so route them to an error branch.

Test on yourself first

Every accepted request mails a real card. Run the workflow once against a record with your own address and check the note in the portal before turning it on.

Field rules, statuses and errors are in the API reference. Prefer another language? See the quickstart.

Send your first note.

Tell us what you want to send and we will set up your workspace.