feat(slack): direct message via email, instead of id

💡 The Idea

Its possible to send dm via email:

msg='the text yall want to send'
user_id="$(curl -X GET -H "Authorization: Bearer $SLACK_TOKEN" \
  -H 'Content-type: application/x-www-form-urlencoded' \
  "https://slack.com/api/users.lookupByEmail?email=$EMAIL" | jq -r .user.id)"

channel_id="$(curl -X POST -H "Authorization: Bearer $SLACK_TOKEN" \
  -H 'Content-type: application/x-www-form-urlencoded' \
  "https://slack.com/api/im.open?user=$user_id" | jq -r .channel.id)"

curl -X POST -H "Authorization: Bearer $SLACK_TOKEN" \
  -H 'Content-type: application/json' \
  --data "$(jq -c -n --arg msg "${msg}" --arg channel "${channel_id}" '{"channel":$channel,"text": $msg}')" \
  https://slack.com/api/chat.postMessage

Credit: https://stackoverflow.com/a/56975663/3797368

This is much more convenient way how to select users, instead of manually finding user`s id…

Thanks

🔨 Breaking Feature

breaking char @

[caronc]

Closing off this issue as content has been merged into the master branch now

[caronc]

I think this is a fantastic idea. It won’t have a breaking feature at all. It’s really easy to detect the difference between an email and a slack user id and an email. so the @ wouldn’t cause an issue at all.

However, it does create a little bit of overhead (as long as you’re aware of it). Slack limits your requests, so depending on how many notifications you’re sending, you’re generating an extra hit to the server unnecessarily each time. I can cache the lookups (after they’re made), but if you’re using the CLI or some kind of web/API service, the instance is destroyed once the message is sent.

Perhaps i could put to the console a Warning message (or INFO) message letting the user know the looked up ID and suggest they consider updating the URL to reflect that? Do you know what I mean?