Overview
For recurring and asynchronous work, you use the SDK tools in your own apps. On its side, the platform receives events from your providers (payments, commerce, email…) and processes them in the background.
There is no general-purpose outbound webhook subscription: you cannot register a URL for Inklura to call your service when a platform event happens. See Inbound Webhooks for what exists and the alternatives.
The mechanisms
| Mechanism | Where it runs | Use it for |
|---|---|---|
| SDK: scheduler, queue, tasks | In your app | Your app's scheduled tasks and background work |
| Platform processing | On the platform | Email sends, SEO, social networks, store sync, automations. You do not drive these directly. |
| Inbound webhooks | https://manage.inklura.fr/api/webhooks/* |
Receiving events from Stripe, WordPress, email or commerce providers |
The SDK in your app
The SDK authenticates your app automatically and keeps its data separate. Three tools cover recurring and asynchronous work:
- Scheduler: runs a task or calls a route of your app on a cron expression. See Scheduled Jobs.
- Queue: a message queue delivered at least once to a handler, with retries and a dead-letter queue. See Queue Workers and SDK → Queue.
- Tasks: long-running jobs with status, progress, and a result. See SDK → Tasks.
Platform processing
The platform processes its own queues in the background: email sends, SEO reports, social network posts, WooCommerce and PrestaShop sync, automation runs. They are not reachable from an app: you act on them through the Platform API (for example by sending a campaign), and the platform handles the rest.
Inbound webhooks
HTTP receivers under https://manage.inklura.fr/api/webhooks/* accept events from Stripe,
WordPress, email providers, commerce platforms, delivery services, and social networks. Each
receiver is specific to its provider: you configure the provider side when you connect the
integration. See Inbound Webhooks for the list and for how the Stripe,
WordPress and PrestaShop receivers authenticate requests.
Which one to use
| Goal | Use |
|---|---|
| Run something on a schedule (daily report, regular check, monthly billing) | Scheduled Jobs |
| Process background work, with retries and a dead-letter queue | Queue Workers |
| Run a long job, beyond a request's time limit | SDK → Tasks |
| Receive an event from Stripe, WordPress, or an email provider | Inbound Webhooks |
| Have Inklura call your external system | Not available as self-serve. See Inbound Webhooks |
Sub-pages
| Page | What it covers |
|---|---|
| Scheduled Jobs | The scheduler: register, list, cancel, securing the called route |
| Queue Workers | Registering a worker, the handler contract, dead letters, job tracking |
| Inbound Webhooks | Receivers per provider, request authentication, outbound pushes |