Package Data | |
---|---|
Maintainer Username: | alek13 |
Maintainer Contact: | github@mak.geek.nz (maknz) |
Package Create Date: | 2018-01-06 |
Package Last Update: | 2022-02-07 |
Home Page: | |
Language: | PHP |
License: | BSD-2-Clause |
Last Refreshed: | 2024-11-23 03:03:31 |
Package Statistics | |
---|---|
Total Downloads: | 3,285,351 |
Monthly Downloads: | 93,346 |
Daily Downloads: | 2,879 |
Total Stars: | 135 |
Total Watchers: | 3 |
Total Forks: | 27 |
Total Open Issues: | 0 |
A simple PHP package for sending messages to Slack with incoming webhooks, focused on ease-of-use and elegant syntax.
supports: PHP 7.0
, 7.1
, 7.2
require: guzzlehttp/guzzle
any of versions ~6.0|~5.0|~4.0
This is the fork of popular, great, but abandoned package
maknz/slack
composer require alek13/slack
hook_url
$client = new Client('http://hook_url')
$client->to('#general')->send('Good morning');
Done!
You can install the package using the Composer package manager by running in your project root:
composer require alek13/slack
Then create an incoming webhook on your Slack account for the package to use. You'll need the webhook URL to instantiate the client (or for the configuration file if using Laravel).
// Instantiate without defaults
$client = new Maknz\Slack\Client('https://hooks.slack.com/...');
// Instantiate with defaults, so all messages created
// will be sent from 'Cyril' and to the #accounting channel
// by default. Any names like @regan or #channel will also be linked.
$settings = [
'username' => 'Cyril',
'channel' => '#accounting',
'link_names' => true
];
$client = new Maknz\Slack\Client('https://hooks.slack.com/...', $settings);
The default settings are pretty good, but you may wish to set up default behaviour for your client to be used for all messages sent. All settings are optional and you don't need to provide any. Where not provided, we'll fallback to what is configured on the webhook integration, which are managed at Slack, or our sensible defaults.
Field | Type | Description
----- | ---- | -----------
channel
| string | The default channel that messages will be sent to
username
| string | The default username for your bot
icon
| string | The default icon that messages will be sent with, either :emoji:
or a URL to an image
link_names
| bool | Whether names like @regan
or #accounting
should be linked in the message (defaults to false)
unfurl_links
| bool | Whether Slack should unfurl text-based URLs (defaults to false)
unfurl_media
| bool | Whether Slack should unfurl media-based URLs, like tweets or Youtube videos (defaults to true)
allow_markdown
| bool | Whether markdown should be parsed in messages, or left as plain text (defaults to true)
markdown_in_attachments
| array | Which attachment fields should have markdown parsed (defaults to none)
$client->send('Hello world!');
$client->to('#accounting')->send('Are we rich yet?');
$client->to('@regan')->send('Yo!');
$client->from('Jake the Dog')->to('@FinnTheHuman')->send('Adventure time!');
// Either with a Slack emoji
$client->to('@regan')->withIcon(':ghost:')->send('Boo!');
// or a URL
$client->to('#accounting')->withIcon('http://example.com/accounting.png')->send('Some accounting notification');
$client->to('#operations')->attach([
'fallback' => 'Server health: good',
'text' => 'Server health: good',
'color' => 'danger',
])->send('New alert from the monitoring system'); // no message, but can be provided if you'd like
$client->to('#operations')->attach([
'fallback' => 'Current server stats',
'text' => 'Current server stats',
'color' => 'danger',
'fields' => [
[
'title' => 'CPU usage',
'value' => '90%',
'short' => true // whether the field is short enough to sit side-by-side other fields, defaults to false
],
[
'title' => 'RAM usage',
'value' => '2.5GB of 4GB',
'short' => true
]
]
])->send('New alert from the monitoring system'); // no message, but can be provided if you'd like
$client->to('@regan')->attach([
'fallback' => 'Keep up the great work! I really love how the app works.',
'text' => 'Keep up the great work! I really love how the app works.',
'author_name' => 'Jane Appleseed',
'author_link' => 'https://yourapp.com/feedback/5874601',
'author_icon' => 'https://static.pexels.com/photos/61120/pexels-photo-61120-large.jpeg'
])->send('New user feedback');
By default, Markdown is enabled for message text, but disabled for attachment fields. This behaviour can be configured in settings, or on the fly:
$client->to('#weird')->disableMarkdown()->send('Disable *markdown* just for this message');
$client->to('#general')->enableMarkdown()->send('Enable _markdown_ just for this message');
$client->to('#operations')->attach([
'fallback' => 'It is all broken, man',
'text' => 'It is _all_ broken, man',
'pretext' => 'From user: *JimBob*',
'color' => 'danger',
'mrkdwn_in' => ['pretext', 'text']
])->send('New alert from the monitoring system');
For convenience, message objects are created implicitly by calling message methods on the client. We can however do this explicitly to avoid hitting the magic method.
// Implicitly
$client->to('@regan')->send('I am sending this implicitly');
// Explicitly
$message = $client->createMessage();
$message->to('@regan')->setText('I am sending this explicitly');
$message->send();
When using attachments, the easiest way is to provide an array of data as shown in the examples, which is actually converted to an Attachment object under the hood. You can also attach an Attachment object to the message:
$attachment = new Attachment([
'fallback' => 'Some fallback text',
'text' => 'The attachment text'
]);
// Explicitly create a message from the client
// rather than using the magic passthrough methods
$message = $client->createMessage();
$message->attach($attachment);
// Explicitly set the message text rather than
// implicitly through the send method
$message->setText('Hello world')->send();
Each attachment field is also an object, an AttachmentField. They can be used as well instead of their data in array form:
$attachment = new Attachment([
'fallback' => 'Some fallback text',
'text' => 'The attachment text',
'fields' => [
new AttachmentField([
'title' => 'A title',
'value' => 'A value',
'short' => true
])
]
]);
You can also set the attachments and fields directly if you have a whole lot of them:
// implicitly create a message and set the attachments
$client->setAttachments($bigArrayOfAttachments);
// or explicitly
$client->createMessage()->setAttachments($bigArrayOfAttachments);
$attachment = new Attachment([]);
$attachment->setFields($bigArrayOfFields);
There is the php-slack/playground
simple console script to test messaging and to see how messages looks really.
If you have any questions how to use or contribute,
you are welcome in our Slack Workspace.
If you're having problems, spot a bug, or have a feature suggestion, please log and issue on Github. If you'd like to have a crack yourself, fork the package and make a pull request. Please include tests for any added or changed functionality. If it's a bug, include a regression test.