slack-client | A better Slack client , with RTM API support | Chat library

ReactPHP core team member here. There are a few options and things going on here.

First off then will never return the value from a promise, it will return a new promise so you can create a promise chain. As a result of that you do a new async operation in each then that takes in the result from the previous one.

Secondly done never returns result value and works pretty much like then but will throw any uncaught exceptions from the previous promise in the chain.

The thing with both then and done is that they are your resolution methods. A promise a merely represents the result of an operation that isn't done yet. It will call the callable you hand to then/done once the operation is ready and resolves the promise. So ultimately all your operations happen inside a callable one way or the other and in the broadest sense. (Which can also be a __invoke method on a class depending on how you set it up. And also why I'm so excited about short closures coming in PHP 7.4.)

You have two options here:

• Run all your operations inside callable's
• Use RecoilPHP

The former means a lot more mind mapping and learning how async works and how to wrap your mind around that. The latter makes it easier but requires you to run each path in a coroutine (callable with some cool magic).

I figured out the problem. The API states:

So I started to suspect that the post message operation from HubSpot is not the same as the one performed by the postman example provided in Slack's website, which only required chat:write:user scope. It turns out that HubSpot post message requires scope chat:write:bot instead.

Yes.

Just send a message with the user ID for channel and it will appear in the slackbot channel of that user.

Something like this:

If you want Slack to show a link to a channel the correct syntax is: