Postmark binding spec

Detailed documentation on the Postmark binding component

Setup Dapr component

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4. name: postmark
  5. namespace: default
  6. spec:
  7. type: bindings.postmark
  8. metadata:
  9. - name: accountToken
  10. value: "YOUR_ACCOUNT_TOKEN" # required, this is your Postmark account token
  11. - name: serverToken
  12. value: "YOUR_SERVER_TOKEN" # required, this is your Postmark server token
  13. - name: emailFrom
  14. value: "testapp@dapr.io" # optional
  15. - name: emailTo
  16. value: "dave@dapr.io" # optional
  17. - name: subject
  18. value: "Hello!" # optional
  • accountToken is your Postmark account token, this should be considered a secret value. Required.
  • serverToken is your Postmark server token, this should be considered a secret value. Required.
  • emailFrom If set this specifies the ‘from’ email address of the email message. Optional field, see below.
  • emailTo If set this specifies the ‘to’ email address of the email message. Optional field, see below.
  • emailCc If set this specifies the ‘cc’ email address of the email message. Optional field, see below.
  • emailBcc If set this specifies the ‘bcc’ email address of the email message. Optional field, see below.
  • subject If set this specifies the subject of the email message. Optional field, see below.

You can specify any of the optional metadata properties on the output binding request too (e.g. emailFrom, emailTo, subject, etc.)

Combined, the optional metadata properties in the component configuration and the request payload should at least contain the emailFrom, emailTo and subject fields, as these are required to send an email with success.

Example request payload

  1. {
  2. "operation": "create",
  3. "metadata": {
  4. "emailTo": "changeme@example.net",
  5. "subject": "An email from Dapr Postmark binding"
  6. },
  7. "data": "<h1>Testing Dapr Bindings</h1>This is a test.<br>Bye!"
  8. }

Warning

The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.

Output Binding Supported Operations

  • create

Related links

Last modified February 16, 2021: Merge pull request #1235 from dapr/update-v0.11 (b4e9fbb)