In yonicd/slackcalls: Generics for Slack API

knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  fig.path = "man/figures/README-",
  out.width = "100%"
)

slackcalls

slackcalls is a part of slackverse

pkgs <- sprintf('slack%s',c('calls','teams','posts','blocks','threads','reprex'))

badges <- sprintf('%s<br>[![](https://github.com/yonicd/%s/actions/workflows/r-cmd-check.yml/badge.svg)](https://github.com/yonicd/%s)',pkgs,pkgs,pkgs)

names(badges) <- pkgs

|||| |:-:|:-:|:-:| ||r badges[pkgs[1]]|| |r badges[pkgs[5]]|r badges[pkgs[2]]|r badges[pkgs[3]]| |||r badges[pkgs[4]]| |||r badges[pkgs[6]]|

slackcalls is the backend of slackverse it interacts with Slack API methods

• Posting
• Querying
• Storage

Posting to Slack

Files

Using files_slack interact with

• files.upload
• files.delete
• files.info
• files.list

Chats

Using chat_slack interact with

• chat.postMessage
• chat.delete
• chat.update

Querying Slack

Using post_slack you can query the API to get information such as the following lists. The functions paginate by default.

Team

• team.info

Users

• users.list
• users.info

Conversations

• conversations.history
• conversations.list
• conversations.info
• conversations.members
• conversations.replies

Storage

slackcalls also saves internally posts that you make during a session in order to use the information for posting to a thread or deleting posts. This mechanism is used in all the slackverse packages.

Stacks

• file_stack: vector of file IDs that have been sent
• post_stack: list of posts that have been sent, contains information of ID, ts and where relevant thread_ts.

The stacks are updated every time a new post/file is sent or deleted.

Last Element

using file_last and post_last you can fetch the head of each stack.

yonicd/slackcalls documentation built on March 12, 2023, 4:38 p.m.