Re: Activity Log API Connector

Level 2 - Champion Alumni

Activity Log API Connector

Does anyone know if there is a way to connect a view of the activity log through the API to a home grown system? Obviously, there would be development work involved, but curious if anyone has tried creating something like a Sales Insight plugin using different methods.

Also, if anyone has been able to connect to a view of the activity log, has anyone tried linking emails sent to show that as well in a pop up window similar to an iFrame or just direct to a Marketo page that shows a view of the email send to that lead?

Thanks for your help!


Not applicable

Re: Activity Log API Connector

I have seen a co-worker recreate MSI with before and make it a stand alone app that can be plugged in anywhere.

Since all activities are available via API, it is definitely possible to do this.

The emails sent would be a little trickier.  You can get the name of the email sent, but the actual email itself would be difficult.  This might be best done with an interesting moment.

Level 2 - Champion Alumni

Re: Activity Log API Connector

Thanks Jamie! When you say plugged in anywhere, does that mean a completely different system (such as a homegrown CRM)? Can you show what this would look like? Would it look similar to the MSI that sits in SFDC?

Thanks again!


Level 9

Re: Activity Log API Connector

Yes, I did this just recently (but probably not very well).

It looked like:

1. Get the authentication token (identity).

2. Lookup an email address and return a lead ID.

3. Get a paging token based on a date

4a. Figure out which activities you want  from the Activities List

4b. Get the Lead Activities with the type returned in 4a and the paging token returned in 3.

Eventually (because I'm actually not a developer), I'll work out how to make it a standalone system that anyone can use.

Level 10 - Community Moderator

Re: Activity Log API Connector

You cannot make real-time calls to the REST API on every page view. You won't have enough calls for this, and that's not what the API is for.

Rather, you will maintain an intermediate cache in {choose your database}. You can query that cache in realtime and perform rate-governed updates from the back end.