github.com/oam-dev/kubevela@v1.9.11/references/docgen/def-doc/workflowstep/notification.eg.md (about) 1 ```yaml 2 apiVersion: core.oam.dev/v1beta1 3 kind: Application 4 metadata: 5 name: first-vela-workflow 6 namespace: default 7 spec: 8 components: 9 - name: express-server 10 type: webservice 11 properties: 12 image: oamdev/hello-world 13 port: 8000 14 traits: 15 - type: ingress 16 properties: 17 domain: testsvc.example.com 18 http: 19 /: 8000 20 workflow: 21 steps: 22 - name: dingtalk-message 23 type: notification 24 properties: 25 dingding: 26 # the DingTalk webhook address, please refer to: https://developers.dingtalk.com/document/robots/custom-robot-access 27 url: 28 value: <url> 29 message: 30 msgtype: text 31 text: 32 content: Workflow starting... 33 - name: application 34 type: apply-application 35 - name: slack-message 36 type: notification 37 properties: 38 slack: 39 # the Slack webhook address, please refer to: https://api.slack.com/messaging/webhooks 40 url: 41 secretRef: 42 name: <secret-key> 43 key: <secret-value> 44 message: 45 text: Workflow ended. 46 lark: 47 url: 48 value: <lark-url> 49 message: 50 msg_type: "text" 51 content: "{\"text\":\" Hello KubeVela\"}" 52 email: 53 from: 54 address: <sender-email-address> 55 alias: <sender-alias> 56 password: 57 # secretRef: 58 # name: <secret-name> 59 # key: <secret-key> 60 value: <sender-password> 61 host: <email host like smtp.gmail.com> 62 port: <email port, optional, default to 587> 63 to: 64 - kubevela1@gmail.com 65 - kubevela2@gmail.com 66 content: 67 subject: test-subject 68 body: test-body 69 ``` 70 71 **Expected outcome** 72 73 We can see that before and after the deployment of the application, the messages can be seen in the corresponding group chat.