Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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.   

            

Use-case
A User in their hydrator 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 user I want to to import Marketo Leads using the HTTP REST API.
  • As a Hydrator 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 user I want to update Marketo Leads and Marketo Static Lists within my pipeline.
  • As a Hydrator 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.   
  • 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

Design 

Design:

 

 

Table of Contents

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

 

  • No labels