SpaceCat Task Processor is a Node.js service that processes messages from the AWS SQS queue SPACECAT-TASK-PROCESSOR-JOBS. Based on the type field in each message, it dispatches the message to the appropriate handler for processing various site-related tasks.

• Receives and processes messages from SQS
• Supports multiple task types via modular handlers
• Built-in handlers for audit status, demo URL preparation, disabling imports/audits, generic agent execution, and Slack notifications
• Extensible and easy to add new handlers

• opportunity-status-processor: Checks and reports status audits for a site
• disable-import-audit-processor: Disables specified imports and audits for a site
• demo-url-processor: Prepares and shares a demo URL for a site
• agent-executor: Runs registered AI/LLM agents (e.g., the brand-profile agent) asynchronously after onboarding flows
• slack-notify: Sends Slack notifications (text or block messages) from workflows

1. Clone the repository
2. Install dependencies:

   npm install

3. Configure AWS credentials and environment variables as needed

• The service is designed to run as a serverless function or background worker.
• It can be invoked in two ways:
  • SQS mode: listens to the SPACECAT-TASK-PROCESSOR-JOBS queue and processes messages automatically (default path for existing workflows).
  • Direct mode: the Lambda entrypoint auto-detects single-message payloads (e.g., from AWS Step Functions) and executes the corresponding handler synchronously. This is used by the new agent workflows to obtain immediate results before triggering follow-up actions.

• To run tests:

  npm test

• To run the optional brand-profile integration test (requires Azure OpenAI env variables):

  npm run test:brand-profile-it

The agent-executor (and the provided brand-profile agent) rely on the Azure OpenAI credentials consumed by @adobe/spacecat-shared-gpt-client. Ensure the following variables are configured in the Lambda/runner environment (and locally when running the IT test):

When invoking the integration test, you can also set BRAND_PROFILE_TEST_BASE_URL to control which site is analyzed and BRAND_PROFILE_IT_FULL=1 to print the complete agent response (otherwise the preview is truncated for readability).

• To lint code:

  npm run lint

To add a new handler:

1. Create a new folder in src/ for your handler.
2. Export your handler function.
3. Add it to the handler mapping in src/index.js.

For more details, see the documentation in src/README.md.

$ npm install @adobe/spacecat-task-processor

See the API documentation.

$ npm install

$ npm test

$ npm run lint

Task processor consumes the SPACECAT-TASK-PROCESSOR-JOBS queue, performs the requested task and sends a notification to Slack as needed.

{ "type": "string", "siteId": "string" }

When the AWS Step Functions Agent Workflow invokes the Lambda directly, it sends the same top-level envelope but without SQS metadata. The payload must include type: "agent-executor" plus the following fields:

{ "type": "agent-executor", "agentId": "brand-profile", "siteId": "123e4567-e89b-12d3-a456-426614174000", "context": { "baseURL": "https://example.com", "params": { "crawlDepth": 2 } }, "slackContext": { "channelId": "C123456", "threadTs": "1731111111.000200" }, "idempotencyKey": "brand-profile-123e4567-e89b-12d3-a456-426614174000-1731111111000" }

Field descriptions:

• agentId (required) – must match a registered agent (e.g., brand-profile).
• siteId (required) – kept at the envelope level for logging/metrics. Agents can still read it from the message passed into agent.persist.
• context (required) – forwarded to agent.run. At minimum it must include baseURL; additional agent-specific params live here.
• slackContext (optional) – when present, the workflow sends pre-/post-execution Slack notifications using channelId and threadTs. Provide an empty object {} if no Slack context is available.
• idempotencyKey (required by workflow) – generated by the caller to deduplicate executions. The task processor treats it as opaque metadata but logs it for traceability.

Any additional properties are passed through to the agent and appear in the executor response body so the workflow can inspect them.