Mailshake
Mailshake is a sales engagement platform designed to streamline and automate cold outreach efforts.
See the
Schema section for a list of objects available for replication.
進一步查看此連接器,包括實用的連結和支援的功能。
| 功能 | 支援詳細資訊 |
|---|
| 支援的 Qlik Talend Data Integration 專案 | 僅複寫專案。不支援資料管道專案。 |
目標更新方法 | 複寫任務: 在資料湖中登陸資料任務: |
管理中繼資料 | 不需要手動產生中繼資料。 |
結構描述演進 | 僅支援變更欄資料類型操作。 |
| LOB 欄 (NCLOB、CLOB 和 BLOB) 複寫 | 不支援。 |
| 已排程 CDC | 必填。此為目標與來源的變更保持同步的方式。 對於複寫任務,請參閱 排程任務 對於湖登陸任務,請參閱 排程湖登陸任務的 CDC |
| 通知 | 部分支援 設定變更進行時的通知 |
| 監控 | 僅限 CDC,因為此連接器與完整載入無關。 監控個別資料任務 |
| 自動解除 JSON 欄裝載的巢狀結構 | 不支援。來源資料集中的 JSON 欄裝載不會在目標上自動解除巢狀結構。 |
Preparing for authentication
To access your data, you need to authenticate the connection with your account credentials.
資訊備註確認您使用的帳戶可讀取您要擷取的表格。
To generate the API key:
- Log into your Mailshake account.
- Go to Extensions > API.
- Click Create API Key to create an API key. Your API key is displayed on the page.
If your account already has an API key, it is displayed in the Your Access section of the page.
- Fill in your API key in the Connection settings page.
Creating the connection
如需詳細資訊,請參閱連線到 SaaS 應用程式。
- 填寫所需的連線屬性。
在連線名稱中提供連線名稱。
選取開啟連線中繼資料以在建立後定義連線的中繼資料。
按一下建立。
Connection settings| Setting | Description |
|---|
| Data gateway | 如您的使用情況有需要,選取 資料移動閘道。 資訊備註此欄位無法用於 Qlik Talend Cloud 啟動器 訂閱,因為不支援 資料移動閘道。若您有另一個訂閱層級且不想使用 資料移動閘道,選取無。 如需關於 資料移動閘道 福利的資訊以及需要此項的使用案例,請參閱 Qlik 資料閘道 - 資料移動。 |
| Start Date | 以 MM/DD/YYYY 格式輸入資料必須從來源複寫到目標的日期。 |
| API Key | API key. |
Schema
資訊備註Schemas and naming conventions can change from version to version. It is recommended to verify your version before continuing.
The schema and info displayed below is for version 1.
Depending on your destination, table and column names may not appear as they are outlined below.
campaigns
The campaigns table contains info about your team’s campaigns.
| Join campaigns with | on |
|---|
| clicks | campaigns.id = clicks.campaign.id campaigns.messages.id = clicks.campaign.id campaigns.messages.id = clicks.parent.message.id |
| leads | campaigns.id = leads.campaign.id campaigns.messages.id = leads.campaign.id |
| opens | campaigns.id = opens.campaign.id campaigns.messages.id = opens.campaign.id campaigns.messages.id = opens.parent.message.id |
| recipients | campaigns.id = recipients.campaignId campaigns.messages.id = recipients.campaignId |
| replies | campaigns.id = replies.campaign.id campaigns.messages.id = replies.campaign.id campaigns.messages.id = replies.parent.message.id |
| sent_messages | campaigns.id = sent_messages.campaign.id campaigns.messages.id = sent_messages.campaign.id campaigns.messages.id = sent_messages.message.id |
| senders | campaigns.sender.id = senders.id |
actionDate
DATE-TIME
|
archived
BOOLEAN
|
created
DATE-TIME
|
endedAt
DATE-TIME
|
id
INTEGER
|
isPaused
BOOLEAN
|
messages
ARRAY
This is a nested data structure: - campaignId: INTEGER
- id: INTEGER
- isPaused: BOOLEAN
- object: STRING
- replyToID: INTEGER
- subject: STRING
- type: STRING
|
object
STRING
|
sender
OBJECT
This is a nested data structure: - created: DATE-TIME
- emailAddress: STRING
- fromName: STRING
- id: STRING
- object: STRING
|
title
STRING
|
url
STRING
|
clicks
The clicks table contains info about recent click activity.
| Join clicks with | on |
|---|
| campaigns | clicks.campaign.id = campaigns.id clicks.campaign.id = campaigns.messages.id clicks.parent.message.id = campaigns.messages.id |
| leads | clicks.campaign.id = leads.campaign.id clicks.recipient.id = leads.recipient.id |
| opens | clicks.campaign.id = opens.campaign.id clicks.parent.message.id = opens.parent.message.id clicks.recipient.id = opens.recipient.id |
| recipients | clicks.campaign.id = recipients.campaignId clicks.recipient.id = recipients.id |
| replies | clicks.campaign.id = replies.campaign.id clicks.parent.message.id = replies.parent.message.id clicks.recipient.id = replies.parent.message.id |
| sent_messages | clicks.campaign.id = sent_messages.campaign.id clicks.parent.message.id = sent_messages.message.id clicks.recipient.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
id
INTEGER
|
isDuplicate
BOOLEAN
|
link
STRING
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
leads
The leads table contains info about the leads in your Mailshake account.
| Join leads with | on |
|---|
| campaigns | leads.campaign.id = campaigns.id leads.campaign.id = campaigns.messages.id |
| clicks | leads.campaign.id = clicks.campaign.id leads.recipient.id = clicks.recipient.id |
| opens | leads.campaign.id = opens.campaign.id leads.recipient.id = opens.recipient.id |
| recipients | leads.campaign.id = recipients.campaignId leads.recipient.id = recipients.id |
| replies | leads.campaign.id = replies.campaign.id leads.recipient.id = replies.parent.message.id |
| sent_messages | leads.campaign.id = sent_messages.campaign.id leads.recipient.id = sent_messages.recipient.id |
| team_members | leads.assignedTo.id = team_members.id |
assignedTo
OBJECT
This is a nested data structure: - emailAddress: STRING
- first: STRING
- fullName: STRING
- id: INTEGER
- last: STRING
- object: STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
created
DATE-TIME
|
id
INTEGER
|
lastStatusChangeDate
DATE-TIME
|
object
STRING
|
openedDate
DATE-TIME
|
recipient
OBJECT
This is a nested data structure: - created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- last: STRING
- object: STRING
|
status
STRING
|
opens
The opens table contains info about recently opened emails.
| Join opens with | on |
|---|
| campaigns | opens.campaign.id = campaigns.id opens.campaign.id = campaigns.messages.id opens.parent.message.id = campaigns.messages.id |
| clicks | opens.campaign.id = clicks.campaign.id opens.parent.message.id = clicks.parent.message.id opens.recipient.id = clicks.recipient.id |
| leads | opens.campaign.id = leads.campaign.id opens.recipient.id = leads.recipient.id |
| recipients | opens.campaign.id = recipients.campaignId opens.recipient.id = recipients.id |
| replies | opens.campaign.id = replies.campaign.id opens.parent.message.id = replies.parent.message.id opens.recipient.id = replies.parent.message.id |
| sent_messages | opens.campaign.id = sent_messages.campaign.id opens.parent.message.id = sent_messages.message.id opens.recipient.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
id
INTEGER
|
isDuplicate
BOOLEAN
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
recipients
The recipients table contains info about the recipients in a campaign.
| Join recipients with | on |
|---|
| campaigns | recipients.campaignId = campaigns.id recipients.campaignId = campaigns.messages.id |
| clicks | recipients.campaignId = clicks.campaign.id recipients.id = clicks.recipient.id |
| leads | recipients.campaignId = leads.campaign.id recipients.id = leads.recipient.id |
| opens | recipients.campaignId = opens.campaign.id recipients.id = opens.recipient.id |
| replies | recipients.campaignId = replies.campaign.id recipients.id = replies.parent.message.id |
| sent_messages | recipients.campaignId = sent_messages.campaign.id recipients.id = sent_messages.recipient.id |
action
STRING
|
campaignId
INTEGER
|
created
DATE-TIME
|
emailAddress
STRING
|
fields
OBJECT
This is a nested data structure. |
first
STRING
|
fullName
STRING
|
id
INTEGER
|
last
STRING
|
object
STRING
|
replies
The replies table contains info about recent replies to your emails.
| Join replies with | on |
|---|
| campaigns | replies.campaign.id = campaigns.id replies.campaign.id = campaigns.messages.id replies.parent.message.id = campaigns.messages.id |
| clicks | replies.campaign.id = clicks.campaign.id replies.parent.message.id = clicks.parent.message.id replies.parent.message.id = clicks.recipient.id |
| leads | replies.campaign.id = leads.campaign.id replies.parent.message.id = leads.recipient.id |
| opens | replies.campaign.id = opens.campaign.id replies.parent.message.id = opens.parent.message.id replies.parent.message.id = opens.recipient.id |
| recipients | replies.campaign.id = recipients.campaignId replies.parent.message.id = recipients.id |
| sent_messages | replies.campaign.id = sent_messages.campaign.id replies.parent.message.id = sent_messages.message.id replies.parent.message.id = sent_messages.recipient.id |
actionDate
DATE-TIME
|
body
STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
externalConversationID
STRING
|
externalID
STRING
|
externalRawMessageID
STRING
|
id
INTEGER
|
object
STRING
|
parent
OBJECT
This is a nested data structure: - id: INTEGER
- message: OBJECT, which is also a nested data structure.
- id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
- object: STRING
- type: STRING
|
plainTextBody
STRING
|
rawBody
STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
subject
STRING
|
type
STRING
|
senders
The senders table contains info about your team’s senders.
| Join senders with | on |
|---|
| campaigns | senders.id = campaigns.sender.id |
created
DATE-TIME
|
emailAddress
STRING
|
fromName
STRING
|
id
STRING
|
object
STRING
|
offerType
STRING
|
sent_messages
The sent_messages table contains info about recently sent emails.
| Join sent_messages with | on |
|---|
| campaigns | sent_messages.campaign.id = campaigns.id sent_messages.campaign.id = campaigns.messages.id sent_messages.message.id = campaigns.messages.id |
| clicks | sent_messages.campaign.id = clicks.campaign.id sent_messages.message.id = clicks.parent.message.id sent_messages.recipient.id = clicks.recipient.id |
| leads | sent_messages.campaign.id = leads.campaign.id sent_messages.recipient.id = leads.recipient.id |
| opens | sent_messages.campaign.id = opens.campaign.id sent_messages.message.id = opens.parent.message.id sent_messages.recipient.id = opens.recipient.id |
| recipients | sent_messages.campaign.id = recipients.campaignId sent_messages.recipient.id = recipients.id |
| replies | sent_messages.campaign.id = replies.campaign.id sent_messages.message.id = replies.parent.message.id sent_messages.recipient.id = replies.parent.message.id |
actionDate
DATE-TIME
|
body
STRING
|
campaign
OBJECT
This is a nested data structure: - created: DATE-TIME
- id: INTEGER
- object: STRING
- title: STRING
|
externalConversationID
STRING
|
externalID
STRING
|
externalRawMessageID
STRING
|
from
OBJECT
This is a nested data structure: - address: STRING
- first: STRING
- fullName: STRING
- last: STRING
- object: STRING
|
id
INTEGER
|
message
OBJECT
This is a nested data structure: - id: INTEGER
- object: STRING
- subject: STRING
- type: STRING
|
object
STRING
|
plainTextBody
STRING
|
rawBody
STRING
|
recipient
OBJECT
This is a nested data structure: - action: STRING
- created: DATE-TIME
- emailAddress: STRING
- fields: OBJECT, which is also a nested data structure.
- first: STRING
- fullName: STRING
- id: INTEGER
- isPaused: BOOLEAN
- last: STRING
- object: STRING
|
subject
STRING
|
to
ARRAY
This is a nested data structure: - address: STRING
- first: STRING
- fullName: STRING
- last: STRING
- object: STRING
|
type
STRING
|
team_members
The team_members table contains info about the individual members of your team.
| Join team_members with | on |
|---|
| leads | team_members.id = leads.assignedTo.id |
emailAddress
STRING
|
first
STRING
|
fullName
STRING
|
id
INTEGER
|
isDisabled
BOOLEAN
|
isTeamAdmin
BOOLEAN
|
last
STRING
|
object
STRING
|
teamBlockedDate
DATE-TIME
|
teamID
INTEGER
|
teamName
BOOLEAN
|