Weave Code
Todoist Laravel Package
laravel-notification-channels/todoist
Laravel notification channel for Todoist, letting you send notifications that create tasks in a Todoist project. Configure the channel and route notifications to your users so alerts, reminders, and app events become actionable Todoist items.
Send Laravel notifications directly to Todoist as tasks. This channel plugs into Laravel's notification system, letting any notifiable model create Todoist tasks through a simple toTodoist() method.
- Task creation from notifications with title, notes, and due dates
- Project targeting via configurable project and section IDs
- Priority and labels support for organizing work
- API token config through
config/services.phpor environment variables - Queue-friendly delivery using Laravel's existing notification pipeline
Frequently asked questions about Todoist
- What does the laravel-notification-channels/todoist package do?
- It is a Laravel notification channel that delivers notifications by creating tasks in Todoist, so alerts, reminders, and events from your application become actionable to-dos. Instead of writing Todoist API calls by hand, you add the channel to a notification class and use Laravel's standard notification API. It is part of the laravel-notification-channels family, which follows consistent conventions across drivers.
- How do I install the Todoist notification channel with Composer?
- Install it with composer require laravel-notification-channels/todoist, which pulls the package and its dependencies into your vendor directory. The service provider is registered through Laravel package auto-discovery, so no manual registration is normally needed. After installing, clear your config cache if you have one cached before configuring credentials.
- How do I configure the Todoist API token for this channel?
- You supply a Todoist API token, typically through a services entry in config/services.php that reads from an environment variable, keeping the secret out of version control. The exact key name and any publishable config file should be confirmed against the package's README and config file in the repository. If you run config:cache in deployment, set the environment variable before caching so the token is baked in correctly.
- How do I send a notification to Todoist from a Laravel app?
- Add the package's channel to the via method of your notification class, then define the toTodoist method that returns the task details such as content and project. The notification is dispatched with the usual Notification facade or the notifiable's notify method. Because it uses Laravel's notification contract, you can route the same notification to other channels at the same time.
- Which Laravel and PHP versions does this package support?
- Support is defined by the illuminate and PHP constraints in the package composer.json and by what its CI matrix actually tests. The available review evidence for this package was insufficient, listing only a 1.0.0 release with an empty changelog, so the supported version matrix could not be verified here. Check the composer constraints and CI configuration directly before assuming compatibility with your Laravel major.
- How do I test Todoist notifications without calling the real API?
- Use Laravel's Notification::fake to intercept notifications and assert they were sent to the expected notifiable, which keeps your test suite offline and deterministic. If the channel sends HTTP requests, you can also use Http::fake to stub Todoist API responses and assert the outgoing payload. Note that fake-based assertions confirm dispatch, not that Todoist accepted the task, so response handling deserves its own test.
- Is this package production ready and actively maintained?
- The evidence available for this package is limited: a 1.0.0 tag with a blank changelog, and no dependency manifest, test suite data, or release history was included in the review material. A first stable major version signals an intent to keep the 1.x API backward compatible, but that is an unverified claim rather than a guarantee. Before production use, pin the version, review the repository's commit and issue activity, and run it through your own staging environment.
- Does the Todoist notification channel require database migrations or schema changes?
- It is an outbound notification driver that creates tasks through Todoist's API, so no database tables of its own should be expected and no migrations should be needed. It also should not interfere with your existing queue or cache schema. Confirm against the published package contents, since a publishable config file is common but migration stubs would be unusual for this type of channel.
- What happens when the Todoist API fails or rate limits are hit?
- Failures surface as exceptions from the HTTP call, which will bubble up through the notification pipeline unless you catch them. Running the notification on a queue lets Laravel's retry and backoff settings absorb transient errors, but a rejected task such as an invalid project ID will fail repeatedly until you fix the payload. Todoist enforces API rate limits, so batching or throttling high-volume notifications is advisable.
- What are the alternatives to using this Todoist notification channel?
- You can call the Todoist REST API directly with Laravel's Http client inside a custom notification channel, which gives full control over payloads and error handling at the cost of more code to maintain. If your goal is simply alerting, built-in channels such as mail, database, or Slack may fit better. Choose this package when you want the task-creation behaviour and laravel-notification-channels conventions without writing the integration yourself.
Weaver
How can I help you explore Laravel packages today?