SQS

Setup Instructions

1. 1

   Create an SQS queue

   In the AWS Console, create a standard or FIFO queue (or use an existing one).

2. 2

   Create an IAM user

   Grant sqs:ReceiveMessage, sqs:DeleteMessage, and sqs:ChangeMessageVisibility permissions on the queue.

3. 3

   Create the connector

   Open the agent, click Add inbound connector, then Create New Connector and select AWS SQS.

4. 4

   Configure and create

   Choose Inbound mode, enter Queue URL, Region, and AWS credentials. Click Create and Connic starts polling the queue.

How Inbound Works

Inbound SQS connectors poll messages from the queue using long polling. When messages arrive, they're parsed and dispatched to all linked agents. After successful processing, messages are deleted from the queue. Failed runs leave messages for retry.

JSON object bodies are enriched with SQS metadata. Other bodies are placed in a message field:

{
  "order_id": "12345",
  "customer_email": "john@example.com",
  "items": ["widget-a", "widget-b"],
  "total": 234.56,
  "_sqs": {
    "message_id": "abc123-def456-ghi789",
    "receipt_handle": "AQEBw...",
    "queue_url": "https://sqs.us-east-1.amazonaws.com/123456789/orders",
    "approximate_receive_count": 1,
    "sent_timestamp": 1705312800000
  }
}

The _sqs metadata includes message ID, receipt handle, queue URL, receive count, and timestamp.

JSON objects can include a files array with each file's name, MIME type, and base64 data. Connic accepts up to 10 complete files, with 10 MiB per file and 10 MiB combined. Invalid optional files are omitted individually. At the first count or size overflow, accepted files remain; that file and all later files are omitted. file_issues records omissions with stable codes, including files omitted to fit the input-review budget. The run can continue even if no optional files remain. Enable Files required under Linked Agents when the task must stop if any file is omitted or no files are present.

• Success: Message deleted from queue after all agents complete successfully
• Failure: Message returns to queue after visibility timeout for retry
• Dead Letter: Configure DLQ in AWS for messages that fail repeatedly

Uses long polling (default 20s) to reduce empty responses and API calls. Set wait time to 0 for immediate responses (higher cost).

Setup Instructions

1. 1

   Create or identify the target SQS queue

   Ensure it exists in the AWS Console.

2. 2

   Create an IAM user

   Grant sqs:SendMessage permission on the queue.

3. 3

   Create the connector

   Open the agent, click Add outbound connector, then Create New Connector and select AWS SQS.

4. 4

   Configure and create

   Choose Outbound mode, enter Queue URL, Region, and AWS credentials. Click Create and results from linked agents will be sent to the queue.

How Outbound Works

Automatic outbound connectors send completed-run envelopes and can be limited to selected inputs. Agent-tool and middleware outbound connectors send only when called. Both patterns are useful for chaining workflows or triggering downstream processing.

{
  "run_id": "550e8400-e29b-41d4-a716-446655440000",
  "agent_name": "order-processor",
  "status": "completed",
  "output": "Order processed successfully. Total: $234.56",
  "error": null,
  "started_at": "2024-01-15T10:30:00Z",
  "ended_at": "2024-01-15T10:30:05Z",
  "token_usage": {
    "input_tokens": 150,
    "output_tokens": 50,
    "thinking_tokens": 0,
    "cached_input_tokens": 0,
    "total_tokens": 200
  }
}

Includes run_id, agent_name, status, output, error, timestamps, and token_usage.

Agent-tool and Middleware Outbound Connectors

An agent-tool outbound connector exposes an editable tool name, defaulting to send_to_<connector_name>. Call a middleware outbound connector by its configured name through send_connector. Both use this connector-owned payload schema:

{
  "payload": {
    "order_id": "12345",
    "status": "approved"
  }
}

payload becomes the SQS message body. Connic applies the configured queue, credentials, FIFO group, serialization, retries, and Bridge routing without exposing those settings to the model.

FIFO Queue Support

For FIFO queues (*.fifo), configure a Message Group ID to maintain ordering. Messages with the same group ID are delivered in order. Automatic deliveries use the run ID as their message deduplication ID.