Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction 

Marketo is a marking automation platform.  Through the Marketo HTTP REST API objects within their platform can be created,retrieved and manipulated with a high degree of customization.   

            Image Removed

Use-case
A User in their hydrator pipeline Data Pipeline can retrieve lead and campaign information, and integrate with other pipeline marketing data to make updates to my objects in Marketo.

User Stories

  • As a Hydrator Data Pipeline user I want to to import Marketo Leads using the HTTP REST API.
  • As a Hydrator Data Pipeline user I want to be import Marketo Leads by Marketo Tags, Marketo Lists (both static and smart), Marketo Campaigns, and Marketo Activities.
  • As a Hydrator Data Pipeline user I want to update Marketo Leads and Marketo Static Lists within my pipeline.
  • As a Hydrator Data Pipeline user I want to update Marketo Opportunities within my pipeline.
  • User should be able to specify client ID and client Secret
  • User should be able to specify identity token, OR use an obtained token after authenticating.   
  • Passwords should not be viewable in plain text from hydrator Data Pipeline studio or pipeline viewer
  • User should be able to obtain error information for connectivity or invalid api calls.   

Example

Example for how the plugin should work

Implementation Tips

  • Tip 1
  •    

Deliverables 

  • Source code in data integrations org
  • Integration test code 
  • Relevant documentation in the source repo and reference documentation section in plugin

Design 

Design: 

 



Table of Contents

Table of Contents
stylecircle

Checklist

  •  User stories documented 
  •  User stories reviewed 
  •  Design documented 
  •  Design reviewed 
  •  Feature merged 
  •  Examples and guides 
  •  Integration tests 
  •  Documentation for feature 
  •  Short video demonstrating the feature