Skip to content

Posting to Slack

EVE Console can post into Slack: the corp Top 10, the monthly summary, sale postings and scheduled tasks. There are two ways in, and you can use both:

  • Connect to Slack — sign in once through your browser. EVE Console then posts as you, under your own name, into any channel you're a member of. This is the usual way.
  • A webhook — a link a workspace hands out that posts into one fixed channel. Use it for a workspace you can't connect to as yourself, such as an alliance Slack that hands out webhooks but not app access.

The settings are in Settings — click the ⚙ gear button in the top-right of the title bar, then open the Slack tab. Discord has its own tab beside it (see Posting to Discord), and the two work side by side.

Nothing is posted until you press a Post to Slack button or set up a scheduled task.

Connect to Slack

  1. On Settings ▸ Slack, click Connect to Slack. Slack opens in your browser.
  2. Sign in to Slack if it asks, and pick the workspace to connect (top-right of Slack's page).
  3. Slack lists what EVE Console asks for: to post messages and upload files as you, and to see the names of your channels. Click Allow.
  4. The browser shows Slack connected. Close the tab and go back to the app.

The status line under the buttons now reads Connected — posting as your name in the workspace, and the channel lists below are filled in.

  • EVE Console never sees your Slack password. Slack sends the browser to a page on eveconsole.com, which hands the approval straight back to the app on your computer; on its own that hand-off is useless to anyone else.
  • The app waits five minutes for you to finish in the browser. If you closed the tab or changed your mind, click Cancel.
  • One workspace at a time. To switch, click Connect to Slack again and pick the other workspace.
  • Some workspaces only allow apps an admin has approved. If Slack says so on its page, ask a workspace admin — or ask for a webhook instead (below).

Try it on yourself first

The channel lists include Note to Self — your own direct message with yourself in Slack. Point a part of the app at it to see exactly what a post looks like before sending one to a channel.

Add a webhook

A webhook comes from whoever runs the workspace: in Slack they add an Incoming Webhook for a channel and give you its link. The link starts with https://hooks.slack.com/services/. A webhook is tied to the one channel it was made for — nothing in EVE Console chooses where it lands.

On Settings ▸ Slack, under Webhooks:

  1. Type a Name — what you'll pick it by, such as "Alliance market".
  2. Paste the link into the URL box.
  3. Click Add.

The webhook now appears in every channel list on this tab, and in the Scheduler, as Webhook: and its name.

A webhook is not the same as being connected:

  • Posts show the webhook's name, not yours — whatever name the workspace gave it.
  • It can't thread. A sale posting's later blocks arrive as separate messages instead of replies under the first.
  • It can't carry a chart. A scheduled task aimed at a webhook skips its chart sections, and says how many it skipped.

There's no Test button for a webhook: the first post shows whether it works. Remove takes one out of the list. It's refused while a part of the app still posts through it (see below) — pick something else there first.

Choose where each part posts

Under Channels, pick where each part of the app posts:

Each list holds your channels, Note to Self among them, then your webhooks. Changes save as you make them. A part's Post to Slack button appears once it has somewhere to post and you close Settings; hovering the button shows where it posts.

  • Private channels are listed only if you're a member. If a channel is missing — new, or just joined — click Reload Channels.
  • Other people's direct messages and group messages aren't listed.

Scheduled tasks don't use these picks: each task chooses its own destination from the same channels and webhooks, followed by your Discord webhooks.

What a post looks like

  • Corp Activity uses the format beside the button. The Top 10 and the monthly summary post in the format picked in the format list next to Post to Slack — the same one Export to Clipboard uses. Pick Slack: headings are bold and tables sit in code blocks, so their columns line up. Plain Text is posted as one code block. The Top 10 is posted without ISK amounts, like Export (No ISK).
  • Sale postings are threaded. Each post block is rendered in Slack's own formatting, whichever format the Posting tab shows. On a channel the first block is the message and the rest go in its thread. Through a webhook each block is its own message.
  • Long posts go out in parts. Slack cuts a long message wherever the length runs out, straight through a table. So the Top 10, the monthly summary and scheduled posts are sent as messages of up to 3,500 characters each, about a second apart, in order. A heading stays with its table, and a section that fits in one message is never split: a table longer than one message is split between rows, with its header repeated at the top of the next message.
  • Charts are uploaded. A scheduled task posting to a channel uploads its chart sections as images, under the message text.

Posting twice

Each Post to Slack button remembers when it last posted. Press it again within 24 hours and EVE Console asks before posting a second time. On Sale Posting this is kept per posting, so posting one listing doesn't hold up another. Slack and Discord keep track separately: posting to one doesn't count as having posted to the other.

Keep it safe

Your connection and your webhook links are secrets

While connected, EVE Console can post as you in any channel you can reach. A webhook link works like a password: anyone who has it can post to its channel.

The Webhooks list in Settings shows each link in full, so don't share a screenshot of the Slack tab, and don't paste a link in chat or in a bug report. If a link leaks, ask the workspace's admins to remove that webhook in Slack, then add the new one here.

  • Disconnect clears the connection from EVE Console. The parts posting to channels lose their Post to Slack buttons; parts set to a webhook keep posting through it.
  • Disconnect doesn't tell Slack. To cut off access completely, remove EVE Console from the workspace's installed apps in Slack as well.
  • The connection, the channel picks and the webhook list are kept in EVE Console's database. On a PostgreSQL setup every client shares them — and so posts as the person who connected.

When a post fails

The status line beside the button (or the task's last-run result in the Scheduler) says what went wrong. Hover a cut-off status line to read all of it. Slack's own reasons are shown as Slack gives them:

  • token_revoked, invalid_auth, account_inactive — the connection is no longer good, usually because it was removed in Slack. Click Connect to Slack again.
  • not_in_channel — you aren't a member of that channel any more. Join it in Slack, or pick another.
  • channel_not_found — the channel was deleted or archived, or you lost access. Click Reload Channels and pick it again.
  • no_service, channel_is_archived, action_prohibited — a webhook was removed, its channel archived, or the workspace blocked it. Ask for a new webhook.
  • Slack has not granted this connection permission to upload files — a chart upload from a connection made before EVE Console asked for that. Click Connect to Slack again.
  • Posted 2 of 3 messages… — the first parts arrived and a later one was refused, even after a second try. The message says why. The parts that arrived stay in the channel; a scheduled run counts as done, so the start isn't posted again.
  • Slack refused it: … — a scheduled post where nothing arrived. The task tries the whole post again on its next pass.
  • That webhook has been deleted. — a scheduled task's webhook was removed from Settings. Removing a webhook isn't stopped by tasks that use it, so pick another destination in the task.

Notes

  • EVE Console only reads the list of your channels, to fill the pickers. It doesn't read messages.
  • Sale postings and corp reports are written in the interface language (see Languages).