SmartSaaS
by @smartsaas
Install via extraDirs (not clawhub). Never auto-add items: only add when user explicitly asks; user defines what to add. Scripts: create-dataset.sh, add-to-d...
scripts/create-dataset.sh "" "" '' (bodyJson includes dataTitle and dataSchema.fields). (2) Parse the response: use the top-level _id as folderId. (3) Add each item: scripts/add-to-dataset.sh '' (itemJson matches schema). (4) Fetch: scripts/get-data-content.sh .scripts/get-schema.sh dataset first to see required/optional fields, then build the body and run scripts/create-dataset.sh "My Dataset" "" '' .scripts/create-dataset.sh "My Dataset". To allow adding content later, include dataSchema: scripts/create-dataset.sh "My Dataset" "" '{"dataTitle":"My Dataset","dataSchema":{"fields":[{"name":"name","type":"string"}]}}'.scripts/list-datasets.sh.scripts/create-project.sh "Project Alpha" "Description".scripts/create-task.sh "" "" "Task title" .scripts/assign-task.sh "" "" "" .scripts/list-integrations.sh.scripts/sync-shopify-products.sh.scripts/refresh-user.sh.scripts/get-calendar-content.sh "2025-03-15".scripts/list-active-campaigns.sh.scripts/start-campaign.sh "" .scripts/create-email-template.sh '{"title":"Welcome","subject":"Hi","content":"..."}'.scripts/create-webpage-template.sh '{"title":"Landing","description":"..."}'.scripts/send-test-email.sh "" "user@example.com" "Test" .scripts/list-knowledge.sh or scripts/list-knowledge.sh 1 10 createdAt desc. Get one: scripts/get-knowledge.sh "" . Create: scripts/create-knowledge.sh '{"title":"My article","content":"..."}'. Post research: scripts/post-research.sh '{"title":"Market study","findings":"..."}'.scripts/dispatch-openclaw-webhook.sh or scripts/dispatch-openclaw-webhook.sh '{"event":"cron","job":"daily"}'.scripts/post-openclaw-event.sh cron '{"schedule":"daily"}'.scripts/configure-openclaw-cron.sh '{"schedule":"0 9 * * *","payload":{},"enabled":true}'.Schema requirements (valid posts): Use the schema chain: run get-schema.sh before any create/post to retrieve the expected shape, then build the request from that output. Schemas are in this skill's schemas/ (JSON per resource); they mirror smartsaas-backend/src/schema/ and repo SCHEMA_REQUIREMENTS.md. Use the correct field names (e.g. task_title, campaign_title, dataSchema) when sending full JSON; scripts may accept friendly names and the API may map them.
Do not log or echo the API key. Never ask the user to provide the API key in chat. If the scripts report missing config, tell the user to set SMARTSAAS_BASE_URL and SMARTSAAS_API_KEY in OpenClaw (e.g. in skills.entries.smartsaas.env in ~/.openclaw/openclaw.json).
SMARTSAAS_BASE_URL and SMARTSAAS_API_KEY must be available to the scripts (see Environment above). The API key is created in SmartSaaS APIScreen. You do not ask the user for it.clawhub install smartsaas-ai