The documentation you are viewing is for Dapr v0.11 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Twilio SendGrid binding spec
Detailed documentation on the Twilio SendGrid binding component
Setup Dapr component
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: sendgrid
namespace: default
spec:
type: bindings.twilio.sendgrid
version: v1
metadata:
- name: emailFrom
value: "testapp@dapr.io" # optional
- name: emailTo
value: "dave@dapr.io" # optional
- name: subject
value: "Hello!" # optional
- name: apiKey
value: "YOUR_API_KEY" # required, this is your SendGrid key
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.apiKey
is your SendGrid API key, this should be considered a secret value. Required.
You can specify any of the optional metadata properties on the output binding request too (e.g. emailFrom
, emailTo
, subject
, etc.)
Example request payload
{
"metadata": {
"emailTo": "changeme@example.net",
"subject": "An email from Dapr SendGrid binding"
},
"data": "<h1>Testing Dapr Bindings</h1>This is a test.<br>Bye!"
}
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
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Last modified July 7, 2022: update nav bar v0.11 (#2633) (b309d3d)