Public Actions
Give integrations access to specific approved operations.
- Version
- 1.1.9
- Released
- 10 November 2026
- Licence
- Commercial
Price £29.00
Check access and installationCheck your application before checkout
What it solves
The problem
Our team needs external tools to submit approved actions and trace their delivery.
What your site gets
The site has controlled integration submissions with dispatch history.
Questions buyers ask
- Which actions can integrations submit?
- External clients can submit only actions allowed by their token and configured protection rules.
- Can a dispatch be replayed?
- Teams can inspect submissions and dispatch attempts and replay dispatches.
- Where are integration controls managed?
- Admins manage action definitions, destinations, tokens and submission history.
Use it in your project
Define the action an integration may submit, scope its token and inspect delivery attempts afterwards. Each destination follows the configured protection rules.
Picture it on your site
For an external integration, define one permitted action and the minimum token scope it needs before allowing delivery. Review a successful attempt and a rejected one in the recorded history. A defined action boundary makes the integration easier to reason about; your application still decides what the action means and how its result is used.
6 captures
Connect repeatable work
- Manage action definitions, destinations and access tokens.
- Review submissions, delivery attempts and replay history.
Is this right for your project?
Automate a bounded piece of work
Choose a repeatable task with a clear input, a permitted action and an observable result. Keep the first workflow small enough that somebody can explain what it is allowed to change. The value is less repeated coordination and a record you can inspect; your application still supplies the registered capabilities, permissions, provider configuration and human decisions that the workflow depends on.
Know how to stop and recover
Try a permitted request, an invalid request and an unavailable dependency in a safe environment. Check which supported operations need confirmation and where their history is recorded. Agree who can pause the workflow and what a retry should do. Connecting a client or enabling a rule is the beginning of the operating process, not proof that every future action is appropriate.
One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.
12 months of protected downloads, updates and included standard support.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Renewal is charged at the price current when you renew. The price is shown before you pay.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Review compatibility and site impact, then follow the installation steps for this package.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens, frontend integration, command-line operations, public routes. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. May connect configured Capell content, media, or integration metadata to the named service boundaries for this package.
- Background work
- A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
- Access controls
- Access-control changes are not described here. Confirm the required roles and grants with the publisher.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Prepare protected Composer access
Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions
-
02
Require the package
composer require capell-app/public-actions -
03
Install the extension
php artisan capell:extension-install capell-app/public-actions -
04
Activate the package licence
In this site’s Admin, open Marketplace, find Public Actions (capell-app/public-actions), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.
-
05
Report the installed package
php artisan capell:marketplace:heartbeat
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.9 Nov 10, 2026
- Recent activity
- 13 approved releases in the last 12 months
Review evidence for this release
Public actions package reviewed with no defects found; anonymous submissions are throttled and mapped through a server-side field definition, while machine endpoints require a token or a verified signature plus an idempotency key.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.9
- Approval date
- Nov 8, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Integration endpoints depend on tokens the site owner issues and rotates; the package cannot detect a token leaked outside the system. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised. The MySQL/MariaDB-specific timestamp-repair branch was reviewed in source but was not executed by this SQLite attestation run.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 13 approved releases-
v1.1.9Nov 10, 2026 -
v1.1.8Nov 2, 2026 -
v1.1.7Oct 28, 2026 -
v1.1.6Oct 20, 2026 -
v1.1.5Oct 17, 2026 -
v1.1.3Oct 9, 2026 -
v1.1.2Oct 8, 2026 -
v1.1.1Oct 8, 2026 -
v1.1.0Oct 7, 2026 -
v1.1.0-beta.41Oct 4, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.