# Slack Integration

## Overview

{% embed url="<https://youtu.be/uCx2mftZ8FE>" %}

This quick start guide will show you how to connect **Stakpak.dev to Slack**\
\
Once integrated, your team can monitor cloud costs, pull logs, trace incidents, scale clusters, rotate secrets, and more directly from Slack.

## Quick Start (< 5 min)

1. Go to [stakpak.dev](https://www.stakpak.dev) and sign in&#x20;
2. On the top right corner, press on your profile icon, then press on settings

<figure><img src="/files/Fu9fhVI7JySuUGKOf7e0" alt=""><figcaption></figcaption></figure>

3. Then press on Integrations

<figure><img src="/files/77pIXOd4Uc2TOQnTGXKW" alt=""><figcaption></figcaption></figure>

4. Here we need to connect both Github and Slack lets start with Github&#x20;

<figure><img src="/files/3cbhRw0TqIaXaiVKeC07" alt=""><figcaption></figcaption></figure>

5. Here you can choose what do you want to give it access it too, then press install

<figure><img src="/files/qZBPcRG10la6nreNQKAd" alt=""><figcaption></figcaption></figure>

6. Now that we connected Github lets connect Slack by pressing connect

<figure><img src="/files/MTNOKm3ydoWOoAreW10v" alt=""><figcaption></figcaption></figure>

7. From here you can choose your slack workspace/make a new one then press allow

<figure><img src="/files/Ky7tfHOAJVYXyQNqeuzB" alt=""><figcaption></figcaption></figure>

8. That's now, let's set up the GitHub Actions Runners

{% hint style="success" %}
GitHub Actions Runners:\
These runners execute your workflows and provide compute resources for your automation tasks.
{% endhint %}

9. Press on the Runners icon from the Left tab

<figure><img src="/files/6is5xjlJ6AvtqJW7Bf47" alt=""><figcaption></figcaption></figure>

10. Press Add Runner&#x20;
    1. Choose the GitHub Repo
    2. Give the Runner and Machine names
    3. Add Labels
    4. Press "Add Cloud Provider"
       1. Choose your Cloud Provider
          1. Fill in the cloud provider configuration&#x20;
    5. Thats it press create runner.

{% hint style="info" %}
If you don't know how to get the OIDC or workload identity federatio,n you can open stakpak in the terminal and ask it to create one for you
{% endhint %}

<figure><img src="/files/BsfWfwzoz9KTjDf5vrN1" alt=""><figcaption></figcaption></figure>

And thats it we are ready to try it 🥳&#x20;

let's go to Slack and type @ Stakpak and ask it something&#x20;

<figure><img src="/files/jpihPa29wrQjTbWa3zsM" alt=""><figcaption></figcaption></figure>

Ops we need to add Stakpak to the channel first, press "Add Them"

Now let's try again👀

<figure><img src="/files/Oa3jwRL2199zQpuHXrgK" alt=""><figcaption></figcaption></figure>

## How Teams Use Stakpak in Slack?

**Monitor cloud costs and performance:**

* How much are we spending on EC2?

**Investigate incidents collaboratively:**&#x20;

* Pull logs, trace errors, or check deployment health without leaving Slack

**Collaborate with your team:**

* Discuss results, make decisions, and rerun commands, all where your team is already talking.

**Automate repetitive DevOps tasks,**&#x20;

* schedule cleanups, rotate keys, scale clusters, or update secrets without switching tools.

and lots more...&#x20;

## Security

You are in control of your security as you choose the privileges you want to give to the runner while creating the OIDC/Workload Identity Federation

### Refrences

* [OIDC Documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html)
* [Workload Identity Federation Documentation](mailto:undefined)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://stakpak.gitbook.io/docs/how-it-works/slack-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.