> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/cloudbeds_outboundqueue.md).

# cloudbeds\_OutboundQueue

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/cloudbeds_OutboundQueue.md).
{% endhint %}

## Description

One Snapfix room change (condition, do not disturb, comments) waiting to be sent to Cloudbeds. Empty on staging.

<details>

<summary><strong>Table Definition</strong></summary>

```sql
CREATE TABLE `cloudbeds_OutboundQueue` (
  `id` int NOT NULL AUTO_INCREMENT,
  `uuid` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `cloudbeds_propertyId` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL COMMENT 'replaces Opera webhook_apikey',
  `cloudbeds_roomId` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `cloudbeds_roomCondition` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL COMMENT 'target: dirty | clean | inspected',
  `cloudbeds_doNotDisturb` tinyint DEFAULT NULL COMMENT 'set DND flag',
  `cloudbeds_roomComments` text CHARACTER SET latin1 COLLATE latin1_swedish_ci COMMENT 'set room comments',
  `cloudbeds_refusedService` tinyint DEFAULT NULL COMMENT 'set refused service flag',
  `cloudbeds_vacantPickup` tinyint DEFAULT NULL COMMENT 'set vacant pickup flag',
  `cloudbedsSynced` tinyint DEFAULT '0' COMMENT '0 = pending, 1 = synced to Cloudbeds',
  `fDeleted` tinyint DEFAULT '0',
  `fCreatedTs` bigint DEFAULT NULL,
  `fModifiedTs` bigint DEFAULT NULL,
  `fDeletedTs` bigint DEFAULT NULL,
  `fServerTs` bigint DEFAULT NULL,
  `uuid_tUser_CreatedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `uuid_tUser_ModifiedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `uuid_tUser_DeletedBy` varchar(255) CHARACTER SET latin1 COLLATE latin1_swedish_ci DEFAULT NULL,
  `retry_count` smallint DEFAULT '0' COMMENT 'Number of failed sync attempts. Marked deleted at 5.',
  PRIMARY KEY (`id`) USING BTREE,
  UNIQUE KEY `uuid` (`uuid`) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=DYNAMIC
```

</details>

## Columns

| Name                      | Type         | Default | Nullable | Extra Definition | Comment                                                 |
| ------------------------- | ------------ | ------- | -------- | ---------------- | ------------------------------------------------------- |
| id                        | int          |         | false    | auto\_increment  |                                                         |
| uuid                      | varchar(255) |         | true     |                  |                                                         |
| cloudbeds\_propertyId     | varchar(255) |         | true     |                  | replaces Opera webhook\_apikey                          |
| cloudbeds\_roomId         | varchar(255) |         | true     |                  |                                                         |
| cloudbeds\_roomCondition  | varchar(255) |         | true     |                  | target: dirty \| clean \| inspected                     |
| cloudbeds\_doNotDisturb   | tinyint      |         | true     |                  | set DND flag                                            |
| cloudbeds\_roomComments   | text         |         | true     |                  | set room comments                                       |
| cloudbeds\_refusedService | tinyint      |         | true     |                  | set refused service flag                                |
| cloudbeds\_vacantPickup   | tinyint      |         | true     |                  | set vacant pickup flag                                  |
| cloudbedsSynced           | tinyint      | 0       | true     |                  | 0 = pending, 1 = sent.                                  |
| fDeleted                  | tinyint      | 0       | true     |                  |                                                         |
| fCreatedTs                | bigint       |         | true     |                  |                                                         |
| fModifiedTs               | bigint       |         | true     |                  |                                                         |
| fDeletedTs                | bigint       |         | true     |                  |                                                         |
| fServerTs                 | bigint       |         | true     |                  |                                                         |
| uuid\_tUser\_CreatedBy    | varchar(255) |         | true     |                  |                                                         |
| uuid\_tUser\_ModifiedBy   | varchar(255) |         | true     |                  |                                                         |
| uuid\_tUser\_DeletedBy    | varchar(255) |         | true     |                  |                                                         |
| retry\_count              | smallint     | 0       | true     |                  | Failed send attempts; the sync skips rows at 5 or more. |

## Viewpoints

| Name                                                                                     | Definition                                                                                                                                                               |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [integrations](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-14.md) | Property management system (PMS) integrations (mappings, room statuses, inbound and outbound queues, webhooks), Deputy, and the keys of the Open API and the vendor API. |

## Constraints

| Name    | Type        | Definition             |
| ------- | ----------- | ---------------------- |
| PRIMARY | PRIMARY KEY | PRIMARY KEY (id)       |
| uuid    | UNIQUE      | UNIQUE KEY uuid (uuid) |

## Indexes

| Name    | Definition                         |
| ------- | ---------------------------------- |
| PRIMARY | PRIMARY KEY (id) USING BTREE       |
| uuid    | UNIQUE KEY uuid (uuid) USING BTREE |

## Relations

```mermaid
erDiagram


"cloudbeds_OutboundQueue" {
  int id PK
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/engineering-reference/db/tables/cloudbeds_outboundqueue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
