One-off jobs are how a Vibe-code agent earns your trust; automations are where it pays rent. These ten workflows run on a schedule or fire when something happens, and they glue OpenProject to the rest of your stack — git, email, calendars, your website, your backups. Each is something you could build yourself with cron and the API, or describe in a single message.

1. Client onboarding from a template, on demand

A new client means a new project, the standard wiki pages, a kickoff meeting, and the right people invited. The agent wraps all of that in one trigger: it clones your template project, renames it, swaps the client’s name into the wiki, creates the kickoff meeting, and mails the team the link. Say: “When I say ‘onboard client Acme’, create a project from the Client Delivery template, invite their team as viewers, and email everyone the project URL.”

2. Git commits that update work packages

Developers forget to update tickets, yet the commit message already contains the work package ID. The agent wires a post-receive hook or a small poller so a commit mentioning OP-123 comments on that work package with the message and a link, and closes it when the message says it fixes the ticket. Say: “Wire our git repo so any commit mentioning a work package number comments on it, and closes it when the message contains ‘fixes’.”

3. Email inbox to work packages

Support mail in a shared inbox goes stale because nobody owns turning it into tasks. OpenProject has no built-in mail collector, so the agent writes one: a small poller that reads the mailbox every ten minutes, opens a Bug work package per new message, and sets the assignee from keywords in the subject. It runs as a service on your server and logs everything it creates. Say: “Check support@ every 10 minutes and open a Bug work package for each new email, assigned to whoever is on the rota.”

4. Morning overdue escalation

Overdue work packages are only a problem if someone actually sees them. A scheduled job scans every morning, comments on anything past its due date addressing the assignee, and emails the project admins a summary. The nudge stops depending on whoever happens to open the right filter that day. After a month of these emails you have a trend instead of a feeling, which is when the capacity conversation finally gets numbers in it. Say: “Every morning at 8, comment on work packages past their due date addressing the assignee, and email each project admin the list.”

5. Monday leadership digest

Cross-project visibility is the reason to run one system instead of five spreadsheets. The agent builds a scheduled query across all active projects — opened, closed, and overdue counts, plus anything due this week — and mails it as a compact table before the leadership call. One email replaces the status meeting’s first twenty minutes. The numbers come straight from the database, so what leadership sees is exactly what the team sees — no manual copy-paste in between. The same job can drop a CSV into a shared folder for whoever prefers files over email. Say: “Every Monday at 7, email the leadership list open and closed counts per project plus everything due this week, sorted by priority.”

6. Website form straight into OpenProject

Your website contact form can land in OpenProject as typed work packages instead of a spreadsheet you export on Fridays. The agent stands up a small webhook endpoint on the server that validates the payload and creates the work package in the right project the moment it arrives. Leads become assignable and trackable while the visitor is still on your site. Say: “Give me a URL I can point my website form at that creates a ‘Sales lead’ work package in the Leads project, due in two days, assigned to Sam.”

7. Deadlines on the team calendar

Milestones and due dates that live only inside OpenProject get missed by the people who live in Google Calendar or Outlook. OpenProject can export calendars as iCal, and the agent assembles one combined feed of every milestone and due date across active projects, then publishes it where the team already looks. Say: “Publish a single iCal feed with all milestones and due dates from active projects so the team sees them in Google Calendar.”

8. Month-end time export for invoicing

If you bill clients by the hour, month-end means exporting logged time per project, and it is never just one click. The agent automates it end to end: query the logged hours, group them by user and work package, write an Excel file into your billing folder, and email you the totals to sanity-check before you invoice. Say: “On the last day of each month, export logged hours per client project to Excel grouped by user, and email me the totals.”

9. Backups that prove themselves

A backup you have never restored is a rumor. The agent sets up a nightly job that dumps the database and archives the attachments with fourteen-day retention, then a monthly job restores the newest dump into a scratch database and reports row counts. You find out the restore path works on a quiet Tuesday, not during an incident. Retention length and an off-site copy are two settings in the same script, so moving a second backup to object storage later is a small change rather than a rebuild. Say: “Back up the database and attachments nightly at 2am, keep 14 days, and on the first of each month restore the newest backup to a scratch database and tell me the row counts.”

10. Changelog from a closed version

Closing a version should produce the release note, not a memory test. The agent watches for version state changes; when a version flips to closed it collects the work packages tagged as changelog-worthy and posts the compiled changelog as project news, with links back to each work package. Say: “When I close a version, compile a changelog from work packages labeled ‘changelog’ and post it as project news.”

See it in action

Official walkthroughs from the OpenProject team:

Worth a watch next:

• Quick Guide: Date alerts — OpenProject’s built-in automatic deadline alerts, the same idea as the scheduled escalation workflows in this list.
• Quick guide: Set up a project list for reporting — how the official team builds saved cross-project reports, a template for the recurring digests described here.

These automations share one pattern: describe the rule once, verify a test run, and let the schedule carry it. Change the rule later by describing the change, the same way it was created. OpenProject on OpenSysLab