Changelog
Follow up on the latest improvements and updates.
RSS
We've just launched our 'like posts' module. Simply give it a Linkedin post URL and it'll automatically like the post, and send you back a bunch of useful info you can use to personalise messages.
Example post:
URL: https://www.linkedin.com/posts/briansolis_kindness-compassion-bekind-ugcPost-6742172694860709889-pHpS/
Response:
[
{
"status": "ok",
"data": {
"firstName": "Brian",
"lastName": "Solis",
"profileUrl": "https://www.linkedin.com/in/briansolis",
"connectionDegree": "2nd",
"numberOfLikes": 6640,
"numberOfComments": 297,
"numberOfViews": 252960,
"postUrl": "https://www.linkedin.com/posts/briansolis_kindness-compassion-bekind-ugcPost-6742172694860709889-pHpS"
}
}
]
We recently added proxy support on all Integromat modules. For those that are keen to use their own proxy when making requests via our modules, you can now simply input your proxy details into Integromat. All traffic will then be routed via your proxy :)
This is an optional field - if you fill out nothing the module will run as normal via our servers as it has in the past.
For API users, you can already pass your proxy via our API in the header:
Growth-Hacking-Proxy: username:password@ip:port
For all you Sales Nav users out there, we've just updated our profile scraper to also return the Sales Nav Profile URL when your scrape.
This is really useful for havin both the regular and Sales Nav profile URLs in your database, mainly for matching and lookups.
Here an example output (see the last row with the Sales Nav profile URL now included):
Request:
[
{
"accounts": "abc",
"profileUrl": "https://www.linkedin.com/in/gauravchand/",
"storeScreenshot": false
}
]
Response:
[
{
"result": {
"connectionDegree": 2,
"connections": "500+",
"description": "As Chief Marketing Officer I am responsible for overseeing the planning, development and execution of Cognizant’s marketing strategy. This includes responsibility for the global marketing organization, strategy and all aspects of Cognizant’s marketing efforts including brand, creative, digital, events, communications, field and channel marketing. My primary mission is to facilitate growth and increase revenue by developing and executing a comprehensive marketing plan that will promote brand recognition and help Cognizant gain a competitive advantage. ",
"fullName": "Gaurav Chand",
"headline": "Chief Marketing Officer and EVP at Cognizant",
"jobDescription": "As Chief Marketing Officer, I am responsible for overseeing the planning, development and execution of Cognizant’s marketing strategy. This includes responsibility for the global marketing organization, strategy and all aspects of Cognizant’s marketing efforts including brand, creative, digital, events, communications, field and channel marketing. My primary mission is to facilitate growth and increase revenue by developing and executing a comprehensive marketing plan that will promote brand recognition and help Cognizant gain a competitive advantage.",
"jobTitle": "Chief Marketing Officer and EVP",
"location": "Denver, Colorado, United States ",
"mutualConnectionsUrl": "https://www.linkedin.com/search/results/people/?facetNetwork=%5B%22F%22%5D&facetConnectionOf=%5B%22ACoAAAA9q6ABQy91dv6OOb8q4kxU9xlJ9E5yjNA%22%5D&origin=MEMBER_PROFILE_CANNED_SEARCH&RESULT_TYPE=PEOPLE",
"imageUrl": "https://media-exp1.licdn.com/dms/image/C4E03AQG-t48Ofs_2dQ/profile-displayphoto-shrink_200_200/0/1526749232893?e=1615420800&v=beta&t=98A4nfqaoO_me5iCjsFgb7xu8EYMyMmjbEX68soFm5s",
"profileUrl": "https://www.linkedin.com/in/gauravchand",
"school": "Southern Methodist University",
"skills": [
{
"name": "B2B Marketing",
"endorsements": "62"
},
{
"name": "Go-to-market Strategy",
"endorsements": "99+"
},
{
"name": "Solution Selling",
"endorsements": "99+"
}
],
"companies": [
{
"url": "https://linkedin.com/company/cognizant/",
"title": "Chief Marketing Officer and EVP",
"name": "Cognizant"
},
{
"url": "https://linkedin.com/search/results/all/?keywords=CenturyLink",
"title": "Chief Marketing Officer and EVP",
"name": "CenturyLink"
},
{
"url": "https://linkedin.com/company/delltechnologies/",
"title": "Senior Vice President, Marketing",
"name": "Dell Technologies"
},
{
"url": "https://linkedin.com/company/dell/",
"name": "Dell",
"title": "Executive Director, Marketing"
},
{
"url": "https://linkedin.com/company/ranbaxy/",
"title": "Brand Executive",
"name": "Ranbaxy"
}
],
"company": "Cognizant",
"firstName": "Gaurav",
"lastName": "Chand",
"salesNavProfileUrl": "https://www.linkedin.com/sales/people/ACoAAAA9q6ABQy91dv6OOb8q4kxU9xlJ9E5yjNA,name,R0_w"
},
"status": "ok"
}
]
We now support usage of your own proxies on both Integromat and our API. This will overwrite the proxies Growth-Hacking.io sets automatically for you, and means you can better control your accounts based on your requirements.
*This is optional and most useful for accounts that want to control login requests on a more granular level. If you have questions, just message us on Slack.
Setup is simple on Integromat:
Inside Integromat each module now has an optional 'Proxy' field, where you can add your settings in the following format:
username:password@host:port
(for example: frank:myPassword@123.456.789.000:5555)
For our API, setup is also simple:
Simply pass in the header the following:
Growth-Hacking-Proxy: username:password@ip:port
See of full documentation here: https://documenter.getpostman.com/view/12720167/TVKA5KFG
improved
New Variable Fields
We've just launched new variable fields you can use to make your messages even more personalized.
Invite & Connect
and Message Sender
- new'$company' - inputs the company name of the profile
- new'$jobTitle' - inputs the job title of the profile
- '$firstName' - inputs first name of the profile
- '$lastName' - inputs first name of the profile
Search & Connect
- '$firstName' - inputs first name of the profile
- '$lastName' - inputs first name of the profile
--> Be aware that you cannot use $company and $jobTitle for Search & Connect, as these fields are not avaiable for us to parse from the search URL screen.
We've just pushed an update that lets you use you li_at cookie directly inside Integromat. Although only a very small % of our users will use this, it's a feature required for getting our public API up and running.
How do I use this?
