skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
sallaapp/salla-partners-agent-kit88 installs

salla-app-functions

Router for building Salla App Functions — serverless TS/JS handlers Salla runs in a sandboxed V8 on store events (e.g. `order.created`, `shipment.creating`). Start here for any App Function task, then follow the step skills: design the trigger, write the handler, validate, test, release. Prefer App Functions over webhooks; act with `salla_functions`. Builds on salla-api-core and salla-webhooks.

How do I install this agent skill?

npx skills add https://github.com/sallaapp/salla-partners-agent-kit --skill salla-app-functions
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill serves as a high-level router and workflow guide for developers building Salla App Functions. It provides a structured step-by-step process for designing, testing, and deploying serverless handlers within the Salla ecosystem using dedicated platform tools.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Salla App Functions

A serverless handler Salla runs automatically on a store event — you write the logic, Salla runs it in a sandboxed V8 runtime. This skill is the router: work the steps in order, each in its own skill, and clear every gate before moving on.

Build flow — route to the step skill

StepDo thisSkill
1Pick the trigger, confirm its payload.data, choose sync vs asyncsalla-app-functions-design
2Write the handler (template, context, Resp, sandbox, timeouts)salla-app-functions-handler
3Keep the template wrapper (first + last line) + type-check locally (before any save)salla-app-functions-validate
4Save (deploys to demo stores)salla-app-functions-release
5Test on a demo store with salla_functions action=preview (read its return value)salla-app-functions-test
6Publish for production (public: app_publish validate → partner submits in Portal; private: salla_private_apps action=publish)salla-app-functions-release

Prefer an App Function over a webhook (when a trigger exists)

  • Secure without signature verification — runs in Salla's sandbox; no inbound request, no X-Salla-Signature.
  • Settings-aware — the merchant's settings arrive in context.settings; no extra fetch.
  • Pre-authenticated — call the Salla Admin API straight from the handler with no Authorization header (no token storage/refresh; token handling is Salla's, not yours → salla-app-auth). Mechanics live in salla-app-functions-handler; for the call itself — base URL, endpoints, scopes, bounded fetch, error shapes — see salla-api-core.
  • Synchronous and actionable — a sync action (e.g. shipment.creating) runs before the operation and your return value shapes or blocks it; a webhook only reacts after.

Fall back to a webhook (salla-webhooks) when no App Function trigger exists, or when the work can't fit the runtime timeouts or the V8 isolate (no npm; no fs/net/http servers/child_process; Web Crypto only; fetch for HTTP) — confirm those limits in salla-app-functions-handler before committing.

Act with the Salla Partners MCP

ToolActionWhat it does
salla_functionslist_triggers get save delete deploy_status previewList triggers; read template + types (.d.ts URLs) + saved content; upsert; delete; poll a deploy; run on a demo store
app_publishopen set validatePublic app: validate the publication (saves a DRAFT; partner submits in Portal) to release the function to real stores
salla_private_appspublishPrivate app: publish (app_id, confirm: true after the partner confirms) to release the function to the requested stores

Sync actions have a hard 5 s total limit (keep each internal async call < 2 s; the docs recommend < 500 ms since the merchant is blocked — a target, not the limit); async events get 30 s. Resp, the entity builders (e.g. Shipment), CommunicationEvent, and all typed contexts are pre-declared runtime globals — use them directly, already in scope. Runtime is a V8 isolate, not Node; module/response specifics live in salla-app-functions-handler.

Step 0 — Discover (ask first)

  1. Which trigger does it run on? (e.g. order.created, shipment.creating)
  2. What should it do when it fires? (notify, sync, validate/block, modify params)
  3. Does it block or change the operation, or just react after the fact?

Key resources

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/sallaapp/salla-partners-agent-kit/salla-app-functions">View salla-app-functions on skillZs</a>