Trigger.dev AI agent for Slack and Teams
Put Wopie to work in Trigger.dev.
Wopie starts Trigger.dev tasks, checks which runs failed and explains the errors in plain words.
$100 in credits · No card needed
Karl in #engineering
@wopie what failed in Trigger.dev since yesterday?
Wopie Quoted 70 credits before starting
12 runs failed out of 3,400. Nine are the same error: the email service timed out between 2 am and 3 am.
Used 63 credits·Answered in #engineering
Karl in #engineering
@wopie why does the invoice export keep failing?
Wopie Quoted 130 credits before starting
It runs out of time on accounts with over 5,000 invoices. It succeeded on 41 of 44 smaller accounts.
Used 118 credits·Answered in the thread
Karl in #engineering
@wopie what happened to run 8421?
Wopie Quoted 45 credits before starting
It finished in 38 seconds and returned 212 rows. No errors and no retries.
Used 40 credits·Answered in the thread
Karl in #engineering
@wopie run the nightly cleanup job now
Wopie Quoted 150 credits before starting
The cleanup job will remove old files for every customer account. I will run it once and post the result.
Used 135 credits·Waiting for your OK
How Wopie works with Trigger.dev.
Wopie is an AI agent that works in Trigger.dev for you. You ask in Slack or Microsoft Teams. It shows which background jobs ran, which failed and why, and starts a job when you ask. Starting jobs that touch customers or money waits for your OK.
- 1Ask in a channelWrite what you need in Slack or Microsoft Teams, the way you'd ask a teammate. No setup in Trigger.dev.
- 2Wopie does the workIt tells you the credits first, then works in Trigger.dev and your other tools, and posts the result in the thread.
- 3You stay in chargeAnything that reaches a customer, moves money or deletes data waits for your OK.
- Works in
- Slack and Microsoft Teams
- Connects
- With your Trigger.dev API key
- Category
- Developer tools
- What it can do
- 10 Trigger.dev actions: 7 look things up, 3 make changes
- Price
- $100 in free credits, then pay per job
Everything Wopie can do in Trigger.dev.
10 Trigger.dev actions, in plain words. You never pick them yourself: ask for the result and Wopie chooses. 7 only look things up. The rest make changes, inside the access you give it.
- Trigger task in bulkChanges
Start multiple runs of one deployed Trigger.
- Execute TRQL QueryChanges
- GetLooks up
Gets a task batch's status, run, completion counts, and item errors.
- Get batch resultsLooks up
Gets the success or failure outcome and encoded output for every run in a completed task batch.
- Get errorLooks up
Gets one Trigger. dev error group's message, occurrence history, affected versions, and resolution or ignore state.
- Get runLooks up
- Get run resultLooks up
Gets one run's compact success or failure result, including its encoded output or error and usage duration.
- List errorsLooks up
Return one forward page of Trigger.
- List runsLooks up
Return one forward page of runs in the connected environment.
- Trigger taskChanges
Start one run of a deployed Trigger.
Safe in Trigger.dev by default.
- Only what you share
Wopie sees only what your Trigger.dev connection allows, and never more than the person who asked.
- Asks before it acts
Looking things up runs on its own. Anything that reaches a customer, moves money or deletes data waits for your OK.
- Every step on record
Each change it makes in Trigger.dev is logged, with who asked and who approved it.
From owners using it
What owners are saying.
“Wopie.ai has transformed how I run the agency. Enquiries, follow-ups and everyday admin are easier to stay on top of, freeing me to focus on our clients and growth. It's simple to use, and the entire operation now runs more smoothly.”
Harcourts · Real estate
“Wopie.ai has genuinely changed how I run Aster Stayz. It saves me hours on everyday tasks, giving me more time to care for our guests and grow the business. It's simple to use and has made the entire operation feel far more manageable.”
Aster Stayz · Short-term rentals
Trigger.dev integration
Trigger.dev questions, answered.
No. It only starts a job when you ask, and risky jobs wait for your OK.
Trigger.dev and its logo belong to their owner and are shown only to say the two work together.