Linkup API for LinkedIn Make integrationAutomate Linkup API for LinkedIn with Make.

This action says yes to an invitation someone sent you, so your network grows without opening LinkedIn. Pair it with a search first, because the module needs to know which invitation to accept.

Posting a comment under a LinkedIn post from a scenario keeps you present in a conversation without switching tabs. The text can come from any earlier module, a sheet row or a template.

Going by its name, this module starts a LinkedIn login through Linkup for a user. The doc gives no detail on what it asks for or returns, so treat it as a technical step rather than an everyday brick.

Once a role is filled, this module closes the job post, so candidates stop applying to an opening that no longer exists. It is the last step in the life of a job managed from Make.

Create Job drafts a new job opening on LinkedIn from data you already have, such as a title and description kept in a sheet. It saves your recruiters from typing the same opening twice.

You get a LinkedIn post published from your account with text mapped from earlier modules. It turns a blog article, a product update or a new event into a post without copy and paste.

This module fetches the contact details of a LinkedIn profile, as its name says. The doc does not list which details come back, so read the first bundle before mapping anything into your CRM.

Feed it a LinkedIn profile and the scenario gets that person's public profile data to reuse, for example to fill a CRM record. It is the building block for enrichment scenarios.

For one company, this module returns its LinkedIn company page data, which gives your account records more context than a bare domain name. Use it next to the profile modules to describe the employer as well as the person.

Reading your LinkedIn inbox from Make lets you copy new conversations to a shared tool where the whole team can see them. Every message thread can then be routed to the right person.

The suggestions LinkedIn makes for your network come back into the scenario, ready to be sorted or sent to a sheet. It is a quick way to review who LinkedIn thinks you should know.

Recruiters get a candidate's resume pulled into the scenario, so it can be stored with the rest of the application. It spares the download and upload dance for each candidate.

Unlike the extraction modules, this one reads the profile of the connected account itself. Handy to confirm which LinkedIn account a scenario is really using before it posts or sends anything.

A like on a chosen post, sent from your account, with no need to scroll the feed. It works well at the end of a chain that has already found the right posts.

When none of the listed modules covers what you need, this one calls any endpoint of the Linkup API with the same connection. It is the way around a missing module, not a module to start with.

Publishing a job makes the opening visible to candidates on LinkedIn. It takes a job you created earlier and puts it live, which keeps the approval step separate from the drafting step.

Pulling the comments of a post into Make shows you who reacted in words, one bundle per comment. From there you can log them, answer them or spot the people worth a conversation.

Looking for companies on LinkedIn from a scenario builds a target list you can then enrich. Results come back one company per bundle, ready for Get Company Information or a sheet.

Your existing LinkedIn connections become searchable data in Make, which helps you find who you already know at a target account. That list is often the fastest route to a warm introduction.

Finding a specific exchange in your LinkedIn messages lets the scenario pick up where a conversation stopped. Where Get Message Inbox reads the inbox broadly, this search narrows to the messages you target.

Invitations waiting for your answer come back as a list, so you can sort them before deciding. It is the natural first step before Accept a Connection Invitation.

The people who reacted to a post turn into a list the scenario can work with, one bundle each. After a launch post, that list tells you who noticed.

This search finds LinkedIn posts on the topic you pick and brings them back one by one. It is the source for monitoring a subject or feeding Like a Post and Add a Comment to a Post.

People matching your search come back as profiles, one per bundle, the raw material for any prospecting list. Chain Extract Profile Information to go deeper on each one.

Recruiting teams can look for candidates from Make and get each match as its own bundle, ready to be scored or stored. It starts the sourcing half of a hiring scenario.

Job posts handled on the recruiter side come back as a list, which gives you a view of every opening in one place. Useful before closing or updating openings in bulk.

An invitation goes out from your account to the profile you map, which turns a found lead into a connection request without a manual click. It is the action most prospecting scenarios end on.

Your scenario can write to a LinkedIn contact directly, with a message built from data of the earlier modules. That removes the copy and paste between your CRM and LinkedIn.

Judging by its name, this module submits a verification code to Linkup, most likely to complete a login started with Authenticate a User. The doc does not describe it further.