eve Slack Agent

The eve Slack Agent template is a deployable starter for building Slack agents with the Eve framework, combining webhook handling, Vercel Connect for credentials, and a TypeScript-defined agent that auto-updates on file changes.

What is the eve Slack Agent template?

The eve Slack Agent template gives developers a working Slack bot scaffold that runs on Vercel and uses the Eve agent framework (beta.eve.dev) to process incoming Slack messages. It accepts Slack events through a webhook, routes them to a starter agent implemented in agent/agent.ts, and responds with the agent's output. The template is published by Vercel Labs as the repository vercel-labs/eve-slack-agent-template, which has 21 stars on GitHub.

Key Features

• One-click Vercel deployment — the repository includes a Deploy with Vercel button that clones the project and connects the Slack connector by setting the SLACK_CONNECTOR environment variable with the webhook path /eve/v1/slack.
• Vercel Connect integration — Slack channel credentials are managed through Vercel Connect, eliminating manual token setup during deployment and local development.
• Starter agent code — the agent's behavior is defined in agent/agent.ts, while a separate agent/instructions.md file holds natural-language instructions and agent/tools/ holds example tools that extend the agent's capabilities.
• Live-reload development — running pnpm dev starts a development server that auto-updates the agent whenever the agent files are edited, so changes are applied immediately.
• Bundled Eve documentation — after installing dependencies, the Eve framework's guides are available offline at node_modules/eve/dist/docs/public/, letting you explore the API without a separate browser tab.
• Simple environment setup — local development uses vercel link and vercel env pull to fetch environment variables from your Vercel project.

Who is it for?

The template is aimed at developers who want to build Slack-integrated AI agents without writing the Slack event-handling infrastructure themselves. It suits teams already using the Eve framework who need a reference pattern for Slack, and Vercel users who want to connect a Slack workspace to their deployment pipeline. Prototypers can use the example tool and instructions to quickly test agent behaviors before adding custom code.

What can you do with the template?

• Customize agent behavior — edit agent/instructions.md to define the agent's persona, rules, and response style, then see changes reflected instantly in the running dev server.
• Add new tools — drop tool implementations into agent/tools/ and reference them from the agent's instruction file to give the bot new actions, such as fetching data or calling external APIs.
• Deploy a live Slack agent — use the Vercel deploy button to clone, connect, and deploy the agent to a production URL, then invite the bot to a Slack channel.

How does the template work?

After cloning and linking the project, vercel link connects the local directory to a Vercel project and vercel env pull downloads environment variables. Running pnpm dev starts the development server that listens for Slack events sent to the /eve/v1/slack webhook. The Eve framework parses each request, applies the instructions from agent/instructions.md, invokes any matched tools, and returns a reply to Slack.

FAQ

Is the eve Slack Agent template free to use?

Yes, the template is open source and free to download from GitHub. Running it requires a Vercel deployment and a Slack app, both of which have their own quotas and pricing.

Do I need a Slack app to use this template?

Yes, you need a Slack workspace and the ability to create a Slack app, because Vercel Connect stores the Slack credentials in the SLACK_CONNECTOR environment variable configured during deployment.

Can I use this template with a different framework?

The template is specifically built for the Eve framework and Node.js; the agent logic is in TypeScript, and the project uses pnpm as the package manager. Reusing the Slack webhook handling in another framework would require porting the Eve integration.

How do I get the environment variables locally?

Run vercel link and then vercel env pull; this pulls the same environment variables that are set in your Vercel project, including SLACK_CONNECTOR configured during deployment.