Reply io
Tables in the Reply io connector
| No | Table Name | Columns | Primary Keys | Read Mode | Inc. Sync Keys | API Info |
|---|---|---|---|---|---|---|
| 1 | campaigns | 14 | Full Refresh | API Reference | ||
| 2 | templates | 5 | Full Refresh | API Reference | ||
| 3 | email_accounts | 4 | Full Refresh | API Reference | ||
| 4 | people | 15 | Full Refresh | API Reference |
Table: campaigns
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | created | VARCHAR | |
| 2 | opensCount | INTEGER | |
| 3 | bouncesCount | INTEGER | |
| 4 | ownerEmail | VARCHAR | |
| 5 | repliesCount | INTEGER | |
| 6 | optOutsCount | INTEGER | |
| 7 | peopleActive | INTEGER | |
| 8 | deliveriesCount | INTEGER | |
| 9 | peopleCount | INTEGER | |
| 10 | outOfOfficeCount | INTEGER | |
| 11 | name | VARCHAR | |
| 12 | id | INTEGER | |
| 13 | peopleFinished | INTEGER | |
| 14 | peoplePaused | INTEGER |
Table: templates
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | subject | VARCHAR | |
| 2 | name | VARCHAR | |
| 3 | id | INTEGER | |
| 4 | body | VARCHAR | |
| 5 | categoryId | VARCHAR |
Table: email_accounts
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | senderName | VARCHAR | |
| 2 | emailAddress | VARCHAR | |
| 3 | signature | VARCHAR | |
| 4 | id | INTEGER |
Table: people
| No | Column Name | Type | Notes |
|---|---|---|---|
| 1 | lastName | VARCHAR | |
| 2 | country | VARCHAR | |
| 3 | city | VARCHAR | |
| 4 | timeZoneId | VARCHAR | |
| 5 | customFields | VARCHAR | |
| 6 | linkedInProfile | VARCHAR | |
| 7 | title | VARCHAR | |
| 8 | firstName | VARCHAR | |
| 9 | phone | VARCHAR | |
| 10 | phoneStatus | VARCHAR | |
| 11 | company | VARCHAR | |
| 12 | id | INTEGER | |
| 13 | state | VARCHAR | |
| 14 | addingDate | VARCHAR | |
| 15 | email | VARCHAR |
External Resources
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.