This integration is concerned with accepting different types of "Product Qualified" leads from the GitLab product and sending them on to Marketo. As of now they come in three different forms
When leads fail to be created we post errors to the slack channel #alerts_pql-sync
. Leads can be retried from the message queue.
Marketo Friendly | Marketo REST API | Field Type | Value |
---|---|---|---|
First name | FirstName | String | variable |
Last name | LastName | String | variable |
Company name | Company | String | variable |
variable | |||
Employees Bucket | Employee_Buckets**c | Employees**c | picklist range |
Phone | Phone | Phone | variable |
Country | Country | String | variable |
State | State | State | variable |
.com Trial Start Date | Trial_Start_Date**c | Date | variable |
Setup for Company/Team Use | Setup_for_Company_Team_Use**c | Boolean | variable |
Product Interaction | productInteraction | string | variable |
Note: These fields may become out of date, you can always see the up to date model in the API documentation which is auto-generated from the actual running code in production.
Gitlab.com
and Customers.gitlab.com
both authenticate with Platypus using OAuth2 Client CredentialsThis integration handles Red Data. The data is stored in the queue and processed by the system. We do not log this data to application logs
Environment | CustomersDot | GitLabDot | Platypus | Workato | Marketo |
---|---|---|---|---|---|
Production | Production | Production | Production | Production | Production |
Staging | Staging | Staging | Staging | Development/Testing | Sandbox |
Development | N/A | N/A | Local Dev & Review Apps | Development | Sandbox |