Put a recurring agent task on a hosted Hermes runtime. Configure instructions, connect supported apps and choose when the work runs through cloudrun's agent panels.
Begin with a task that has a clear input, a useful output and a person who can review the result.
Hermes available today. View hosting pricing
What you can configure
Use the agent's instructions and Skills to define the task, the output format and when it should ask for more information.
The Integrations panel provides connections such as Gmail, Slack and GitHub. Check the exact actions and account permissions needed for your workflow before enabling it.
Automations combine a prompt, cron schedule and delivery destination. Test the prompt interactively before enabling the recurring run.
Connect a supported channel such as Telegram, Slack or email when the workflow needs people to message the agent.
From setup to useful work
For example, prepare a draft summary from approved material. Decide what a successful result must contain.
Set up your organization and project, then open the default Hermes agent on the canvas.
Connect only the services required for that task. Run a harmless sample in chat.
Check the source material, output and destination. Try missing information and an unauthorized request as well as the ordinary case.
Add the required schedule or channel, then verify a complete run and document who will maintain it.
A resource you can use today
Record account ownership, permissions, expected results and recovery steps. Use the client-agent launch checklist to decide what is ready and what still needs a test.
Reusable worksheet. No signup required.
Make the next decision
Choose an approved set of source material. Ask the agent to prepare a short brief that identifies its sources and flags missing information. Send the draft to the agreed reviewer using a supported delivery path. This is a workflow idea to configure and test; confirm source access and delivery in your account.
Before you get started
The quickstart uses the workspace, project and agent panels to configure integrations, skills, tools, schedules and channels. A custom tool or unsupported integration may require development work. Review the exact workflow before promising a fully no-code delivery.
A native n8n or Make integration is not established by the current documentation. If either system is part of your workflow, verify the connection method, authentication and complete workflow before relying on it.
Yes. The Automations panel lets you specify a prompt, cron schedule and result destination. Check the timezone, next run and delivery result in your actual setup.
Agree on account ownership and authorized access first. Connect supported accounts through the relevant configuration flow and record who can renew or revoke access. Keep secret values out of handoff documents.
Test the ordinary request, missing input, denied access, unavailable integration and duplicate delivery. Record the expected result, what happened and who accepted it. Include the operating and model costs in the workload estimate.
Use the client launch checklistYour first project
Create a project, test the agent's result and configure the delivery path your customer will actually use.