PHPackages                             jorbascrumps/laravel-queue-it - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. jorbascrumps/laravel-queue-it

ActiveLibrary[Queues & Workers](/categories/queues)

jorbascrumps/laravel-queue-it
=============================

Queue-it integration for Laravel

2.0.0(7mo ago)2219↑75%[1 PRs](https://github.com/jorbascrumps/laravel-queue-it/pulls)MITPHPPHP >=8.0CI passing

Since Sep 2Pushed 6mo ago1 watchersCompare

[ Source](https://github.com/jorbascrumps/laravel-queue-it)[ Packagist](https://packagist.org/packages/jorbascrumps/laravel-queue-it)[ Docs](https://github.com/jorbascrumps/laravel-queue-it)[ GitHub Sponsors](https://github.com/jorbascrumps)[ RSS](/packages/jorbascrumps-laravel-queue-it/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (5)Dependencies (3)Versions (7)Used By (0)

Laravel Queue-it
================

[](#laravel-queue-it)

[![Tests](https://github.com/jorbascrumps/laravel-queue-it/actions/workflows/run-tests.yml/badge.svg)](https://github.com/jorbascrumps/laravel-queue-it/actions/workflows/run-tests.yml/badge.svg)

Queue-it integration for Laravel.

```
use Illuminate\Support\Facades\Route;

Route::view('/event', 'event')->middleware('queue-it.known-user-queue');
```

Installation
------------

[](#installation)

```
composer require jorbascrumps/laravel-queue-it

```

Setup
-----

[](#setup)

Add your Queue-it credentials to your environment file.

```
QUEUE_IT_CUSTOMER_ID=
QUEUE_IT_SECRET_KEY=
```

Tip

Your secret can be found in the [Go Queue-it self-service platform](https://go.queue-it.net) under *Account > Settings > Integration*.

Usage
-----

[](#usage)

### Known User Queue

[](#known-user-queue)

Caution

You should not apply `KnownUserQueue` to static or cached pages, or assets.

Known User Queue allows control over queues via the Go Queue-it self-service platform and requires an integration config. See [Exporting integration config](#exporting-integration-config) for details on how you can acquire it. Once you've added an integration config to your project you can apply the `KnownUserQueue` middleware to any route or route group that you want to be queueable.

```
use Illuminate\Support\Facades\Route;

Route::view('/event', 'event')->middleware('queue-it.known-user-queue');
```

You can also reference the class name instead of the alias if you prefer:

```
use Illuminate\Support\Facades\Route;
use Jorbascrumps\QueueIt\Http\Middleware\KnownUserQueue;

Route::view('/event', 'event')->middleware(KnownUserQueue::class);
```

### Inline Queue

[](#inline-queue)

Caution

You should not apply `InlineQueue` to static or cached pages, or assets.

Apply the `InlineQueue` middleware to any route or route group that you want to be queueable. You must specify an event and queue domain. Other customization options are also available.

```
use Illuminate\Support\Facades\Route;
use Jorbascrumps\QueueIt\Http\Middleware\InlineQueue;

Route::view('/event', 'event')->middleware([
    InlineQueue::eventId('event1')
        ->queueDomain('jorbacrumps.queue-it.net')
]);
```

User queue eligibility
----------------------

[](#user-queue-eligibility)

You may not want to send every user through the queue. In these scenarios you can provide a customer resolver to determine queue eligibility within a service provider.

```
KnownUserQueue::resolveUserQueueEligibilityUsing(function (Authenticatable $user) {
    return ! $user->isAdmin();
});
```

The callback will be resolved via the container so you can inject the authenticated user or any other depedency you may need.

Exporting integration config
----------------------------

[](#exporting-integration-config)

Known User Queues require an integration configuration file that contains logic for how and when queues should be managed. There are several options available to add this file to your project.

### Publish webhook

[](#publish-webhook)

This package includes a webhook route that you can register in your account to push your integration configuration file to anytime you make changes. You can configure this setting under *Integrations > Overview > Settings > Publish web endpoint*.

Tip

You can customize the webhook route in your environment file:

```
QUEUE_IT_CONFIG_UPDATE_URL=/webhooks/queue-it/config-published

```

### Using Artisan

[](#using-artisan)

This package includes an Artisan command to fetch and store your integration file anytime you need to. Note that this method requires an API key.

```
php artisan queue-it:fetch-config

```

Important

You can specify your API key in your environment file:

```
QUEUE_IT_API_KEY=your-api-key

```

### Custom resolver

[](#custom-resolver)

If you need to implement custom logic to provide your integration configuration you may do so using a custom resolver in a service provider.

```
KnownUserQueue::resolveIntegrationConfigurationUsing(function () {
    // Return your integration configuration as a JSON string
});
```

The default resolver provided will attempt to find your configuration in your application's storage.

### Manual download

[](#manual-download)

Download options can be found in your account under *Integrations > Overview > Latest KnownUser configuration*. You should save this to your application's storage directory.

### Customizing config file location

[](#customizing-config-file-location)

By default, your integration configuration file is expected to be found in your application's storage as `queue-it-config.json`. If you need to store it under a different name in storage, you can specify this in your environment file:

```
QUEUE_IT_CONFIG_FILE=queue-it-config.json
```

###  Health Score

37

—

LowBetter than 83% of packages

Maintenance65

Regular maintenance activity

Popularity18

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~95 days

Total

5

Last Release

233d ago

Major Versions

1.3.0 → 2.0.02025-09-19

PHP version history (2 changes)1.0.0PHP >=7.4

2.0.0PHP >=8.0

### Community

Maintainers

![](https://www.gravatar.com/avatar/97c55fed442de665a520fbe2386c404831519d8e8f0a9c3b37296caa4b105be3?d=identicon)[jorbascrumps](/maintainers/jorbascrumps)

---

Top Contributors

[![jorbascrumps](https://avatars.githubusercontent.com/u/5909516?v=4)](https://github.com/jorbascrumps "jorbascrumps (46 commits)")

---

Tags

middlewarelaravelqueue-itlaravel-queue-it

### Embed Badge

![Health badge](/badges/jorbascrumps-laravel-queue-it/health.svg)

```
[![Health](https://phpackages.com/badges/jorbascrumps-laravel-queue-it/health.svg)](https://phpackages.com/packages/jorbascrumps-laravel-queue-it)
```

###  Alternatives

[harris21/laravel-fuse

Circuit breaker for Laravel queue jobs. Protect your workers from cascading failures.

3786.5k](/packages/harris21-laravel-fuse)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)