> ## Documentation Index
> Fetch the complete documentation index at: https://docs-dev-actions-triggers-prototype.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
> Learn how to write an Action, which includes choosing a flow, creating an Action and configuring it, and binding it to the flow.
# Write Your First Action
This guide will walk you through how to create and deploy your first Action using the Auth0 Dashboard. When you finish, you should understand the basic functionality that you will use with all Actions and you will be familiar with the programming model. What you will learn constitutes the foundation of writing any Action, regardless of its purpose or the flow.
## The goal: notify Slack on user login
You are creating an Action that sends a message to a Slack channel when a user logs in. While this tutorial will use the Post Login trigger, the information provided here is useful for triggers of any type.
To accomplish this task, you will do the following:
* [Create an Action](#create-an-action)
* [Add a Secret](#add-a-secret)
* [Add a dependency](#add-a-dependency)
* [Save the Draft](#save-the-draft)
* [Add custom logic](#add-custom-logic)
* [Test an Action](#test-an-action)
* [Deploy an Action](#deploy-the-action)
* [Attach an Action to a Flow](#attach-the-action-to-a-flow)
* [See the results of an Action in Tenant Logs](#observe-actions-in-tenant-logs)
## Prerequisites
Because this Action will be sending messages to a Slack channel, you need to [create an Incoming Webhook for a Slack Workspace](https://api.slack.com/messaging/webhooks). Once you have a Slack Webhook URL, you may continue with this guide.
## Create an Action
To get an Action working in a specific flow, you need to create the Action and then add it to a flow.
1. Navigate to [Auth0 Dashboard > Actions > Library,](https://manage.auth0.com/#/actions/library) then select **Create Action** > **Build from scratch**.
2. Enter a **Name** and select the **Login / Post Login** trigger since you’ll be adding an Action to the Login flow, then select **Create.**
The Actions Code Editor appears:
## Create an Action from a Template
The Actions Template gallery offers a variety of starter templates on their way to creating an Action. To create an Action from a Template:
1. Navigate to [Auth0 Dashboard > Actions > Library](https://manage.auth0.com/#/actions/library), then select **Create Action.**
2. Select **Choose from template**.
3. Select the template that you would like to use for building an Action.
4. You should now see a read-only preview of the code within the template. To proceed, select **Use this template**.
5. Enter a name, and select **Create**.
## Add a Secret
Each Action can contain Secret values, which are suitable for holding sensitive information, such as Access Tokens and API Keys. Let’s store the Slack Webhook URL as a Secret.
1. Select the Key Icon from the code editor's left sidebar
2. Select **Add Secret**.
3. Give the Secret the following name: `SLACK_WEBHOOK_URL`.
4. Paste in the Webhook URL provided by Slack and select **Create**.
You’ll see that the Secret has been added to the Action and you can use the new secret via intelligent code complete by typing `event.secrets`.
Once a Secret has been created, its value will never be revealed. Auth0 encrypts all Secrets and stores them securely.
## Add a dependency
You’ll be using the [`@slack/webhook` `npm` package](https://www.npmjs.com/package/@slack/webhook) to make it easy to send a message to Slack. You can use nearly any public `npm` package in an Action as long as it can be installed without relying on [native add-ons](https://www.npmjs.com/package/node-gyp).
To add the dependency:
1. Select the Dependency icon (cube icon) in the sidebar.
2. For **Name**, enter `@slack/webhook`.
By default, your Action will use the latest version of the dependency at the time the dependency was added.
3. Select **Create**, and the Dependency should be added to the Action:
When you save this Action, the latest version of your dependency will be resolved and replaced with a specific version number to keep future updates to the package from breaking your Action.
## Save the Draft
Select **Save Draft**. Your Action is saved, but it won’t be executed as part of any user flows yet. With Actions, you have the opportunity to create, edit, and test Actions before they affect any traffic in your Auth0 tenant. Once you’re happy with the behavior of the Action, you’ll deploy the Action and add it to a Flow later.
## Add custom logic
Now that the Action has been configured with a Secret and a dependency, let’s write some code!
Every Action has an event object that contains read-only, contextual information relevant to the associated trigger. If you start typing `event.` in the Editor, you should be presented with all the available properties of the event. To learn more about which information is available on each trigger, read [Explore Flows and Triggers](/docs/customize/actions/explore-triggers).
Let’s use our Action to notify Slack. Add this code to your action:
```javascript lines theme={null}
const { IncomingWebhook } = require('@slack/webhook');
exports.onExecutePostLogin = async (event, api) => {
const url = event.secrets.SLACK_WEBHOOK_URL;
const webhook = new IncomingWebhook(url);
// Send the notification
await webhook.send({ text: "Logging In..." });
};
```
Select **Save Draft** to save your Action.
## Test the Action
Before you run this Action in your tenant with real user traffic, test it to ensure it behaves as expected.
1. Select the Test (triangle) icon in the sidebar. In the Payload section, you’ll see editable JSON data relevant to the trigger that you selected when you created the Action.
2. Select the **Run** button, and you should see a message appear in your Slack channel.
## Deploy the Action
Now that we’re satisfied that the Action is working as expected, it’s time to deploy it.
Select **Deploy**. Deploying an Action takes a snapshot of the Action at that time and records it as an **Action Version**.
Select **Version History**, and you should see the Action recorded as Version 1:
You are now free to update your Action and save it without affecting Version 1 of your Action. Auth0 will only execute the currently deployed version of an Action, so until you deploy an action again, Version 1 will be executed by Auth0.
## Attach the Action to a Flow
The final step in configuring a new Action so that it’s executed as part of your tenant’s traffic is to attach it to a Flow.
1. Navigate to [Auth0 Dashboard > Actions > Flows](https://manage.auth0.com/#/actions/flows) to see a list of the available Flows:
2. Select the [Login flow](/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger) and drag `my-slack-action` into the flow.
3. Select **Apply**.
The Action is now running for real user traffic within your tenant. If you’d like a more robust testing environment, consider [setting up multiple Auth0 environments](/docs/get-started/auth0-overview/create-tenants/set-up-multiple-environments).
## Observe Actions in Tenant Logs
Now that your Action is running as part of the Login flow, Auth0 captures information about each Action execution in the tenant logs. To view this, navigate to [Auth0 Dashboard > Monitoring > Logs](https://manage.auth0.com/#/logs), and select a **Successful Login** event.
You should see an **Action Details** view that contains information about any Actions that were executed as part of that flow.
## Next steps
Now that you’ve written your first Action, check out [Explore Flows and Triggers](/docs/customize/actions/explore-triggers) to learn how to perform some common tasks with Actions.