cicada
Start free
Developer tools · Connects with an API key

An AI teammate for Trigger.dev.

Connect Trigger.dev and your Cicada agent works in it for you: 10 Trigger.dev actions, from looking things up to making changes. Ask from iMessage, WhatsApp, Slack or the app, and keep it read-only if you only want it to look.

Start free

300 free credits. No card. Read-only if you want.

Things to ask about Trigger.dev
  • What broke in Trigger.dev overnight, and is it new?
  • Open a Trigger.dev issue for this bug with the steps from the Slack thread.
  • Summarise this week's Trigger.dev activity for the standup.
  • Tell me when something in Trigger.dev needs my attention.
Text it, Slack it, or type it in the app. Swap in your own details.
What Cicada can do in Trigger.dev

10 Trigger.dev actions, picked for what you ask.

About Trigger.dev: Trigger.dev is a platform for building, deploying, and managing reliable background tasks and workflows.

Reads

8 in all · always allowed
  • Get Run
    Retrieve one run's status, timing, payload, output, attempts, metadata, relationships, schedule,…
  • Get Error
    Retrieve one Trigger.dev error group's message, occurrence history, affected versions, and…
  • List Runs
    Return one forward page of runs in the connected environment, optionally filtered by time, status,…
  • List Errors
    Return one forward page of Trigger.dev error groups, optionally filtered by task, version, status,…
  • Get Run Result
    Retrieve one run's compact success or failure result, including its encoded output or error and…
  • Execute TRQL Query
    Run one read-only Trigger.dev Query Language SELECT statement for custom run analytics and return…
  • Get Batch
    Retrieve a task batch's status, run IDs, completion counts, and item errors.
  • Get Batch Results
    Retrieve the success or failure outcome and encoded output for every run in a completed task batch.

Changes

2 in all · off when Trigger.dev is read-only
  • Trigger Task
    Start one run of a deployed Trigger.dev task and return the new run ID.
  • Batch Trigger Task
    Start multiple runs of one deployed Trigger.dev task in one provider-side batch and return the…

Showing 10 of 10. Your agent can use every one of them; you don't pick them, you ask for the outcome.

How it works

Connected in a minute. In your control after that.

  1. Connect Trigger.dev

    Open Connections, find Trigger.dev and paste an API key from your Trigger.dev account settings. Cicada checks it works before saving it.

  2. Choose what it may do

    Full, Ask first or Read-only, for the whole workspace. Share Trigger.dev with the team, or keep it under each person's own login.

  3. Ask from anywhere

    Text your agent on iMessage or WhatsApp, message it in Slack or the app, or put a Trigger.dev job on a schedule: every morning, every Friday.

Works with your other tools

Trigger.dev, together with the rest of your stack.

Ask for an outcome that spans apps and your agent pulls from each one, cross-checks them and sends back one answer.

More developer tools integrations

GitHub integrationPagerDuty integrationSentry integrationHugging Face integrationDaytona integrationGitLab integrationBitbucket integrationStack Exchange integration

Often used alongside

Gmail integrationSlack integrationGoogle Sheets integrationGoogle Calendar integration

See all 888 integrations

Questions

Trigger.dev and Cicada, answered.

Does Cicada integrate with Trigger.dev?

Yes. Trigger.dev is one of the 888 apps with a page here, and it connects with an API key. Once it's connected, every agent in your workspace can use it from any channel you talk to them on.

How do I connect Trigger.dev?

Open Connections, find Trigger.dev and paste an API key from your Trigger.dev account settings. Cicada checks it works before saving it.

What can Cicada do in Trigger.dev?

10 actions: 8 that read from Trigger.dev and 2 that change things in it, for example get run, get error, list runs. It picks the right ones for what you ask and chains them with your other apps.

Can I stop Cicada changing things in Trigger.dev?

Yes. In Connections, set Trigger.dev to Read-only and no agent in your workspace can create, change or delete anything in it; it can still read. Ask first lets it act but makes it check with you before each change.

Can I ask about Trigger.dev from my phone?

Yes. Text your agent on iMessage or WhatsApp, or message it in Slack or the app. It answers in the same thread, and it can run Trigger.dev jobs on a schedule, like every morning at 8.

Is my Trigger.dev data safe?

Your Trigger.dev login or key is stored on the server and never appears in a conversation. Disconnecting removes it. Every action an agent takes is in your activity log, and your data isn't used to train models.

One teammate. The output of a team.

Works nights, remembers every decision, answers in the thread. Start free with 300 credits.

Start free