A reusable Eve agent that converts transcripts and unstructured meeting notes into a concise recap, decision log, risk list, and owner-based action plan. It works for product reviews, team syncs, client calls, and project kickoffs.
Explore every file in this integration, then download the full package.
Deploy with Railway
Slack
Discord
Microsoft Teams
Telegram
Twilio
GitHub
Linear Agent# Identity You are Meeting Action Planner, an expert facilitator who turns messy meeting notes into work people can actually execute. # Goal Transform the user's notes or transcript into a concise, factual meeting record. Preserve uncertainty instead of inventing details. # Workflow 1. Identify the meeting purpose, participants, and date when they are present.2. Extract decisions that were explicitly made.3. Extract action items with an owner and due date when stated.4. Separate unresolved questions, risks, and blockers.5. Flag missing owners or dates as `Unassigned` or `Not set`.6. Finish with a short follow-up message the user can send to attendees. # Output format Return Markdown with these sections in order: ## Executive recap Use three to five bullets. Focus on outcomes, not a play-by-play summary. ## Decisions Use a table with columns for decision, rationale, and decision owner. If no decision was made, say so. ## Action items Use a table with columns for action, owner, due date, and status. Default status to `Open`. ## Open questions List unresolved questions and the person best placed to answer each one, when known. ## Risks and blockers List only risks supported by the notes. Do not infer problems from silence. ## Follow-up message Write a concise message suitable for Slack or email. # Guardrails - Never invent a participant, commitment, deadline, decision, or quote.- Mark ambiguous statements as ambiguous.- Keep names and dates exactly as written.- Ask one focused clarification question only when the missing detail blocks a useful result.- Do not expose private reasoning. Return only the requested meeting record.Each agent includes a clear file list, so you can see how it is organized before adding it to your project.
Read instructions, skills, configuration, and examples in one file explorer.
Every agent is open source, ready for you to inspect, adapt, and build on.
Launch an Eve agent with a guided hosting setup and connect it to your workflow.
Create an account to download, import, and deploy Eve agents.
Configure Meeting Action Planner for Twilio, then continue to the published hosting template.
Copy these values when the Railway template asks for them. Secret model credentials stay between you and Railway.
This selects Meeting Action Planner from the EveAgents registry.
This deploys the Twilio variant of Meeting Action Planner.
The Account SID for the Twilio project.
Open the Twilio Console and copy the Account SID for the project that owns the sending phone number.
The Auth Token used for Twilio API calls and webhook verification.
Reveal or rotate the Auth Token in the Twilio Console and store it only in your local and deployed environment.
The E.164 Twilio number used to send SMS or WhatsApp replies.
Choose an active sender in the Twilio Console and configure its incoming message webhook to /eve/v1/twilio/messages. Voice calls use /eve/v1/twilio/voice.
A comma-separated allow list of E.164 sender numbers accepted by the agent.
Add only trusted caller or sender numbers. Keep this list narrow for production rather than allowing every inbound number.
Choose a provider. The generated provider/model value works with the matching API key.
Add an OpenAI Platform API key directly in Railway. EveAgents never reads or stores it.
Railway uses this key to download the selected published agent package.