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 | ユース ケースに応じて Data Movement gateway を選択します。 情報メモQlik Talend Cloud スターター サブスクリプションでは Data Movement gateway をサポートしていないため、この項目は使用できません。別のサブスクリプション ティアを利用しており、Data Movement gateway を使用しない場合は、 [None] (なし) を選択します。 Data Movement gateway の利点とそれを必要とするユース ケースの詳細については、「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
|