Build it
What do you want Docparser and LinkedIn to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Docparser and LinkedIn
Triggers and actions 2 triggers ยท 5 actions
Trigger
Parsed Document Data AvailableTriggers whenever a new Document is processed and parsed data is available.
- Parsed Table Row Available
Triggers whenever a new Document is processed and parsed table rows are available.
- Fetch Document From URL
Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
- Upload Document
Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
Action
Create Linked In PostCreates a new post on linkedin for the authenticated user or an organization they manage; ensure the user has necessary permissions if posting for an organization.
- Delete Linked In Post
Deletes a specific linkedin post (share) by its unique `share id`, which must correspond to an existing share.
- Get My Info
Fetches the authenticated linkedin user's profile, notably including the 'author id' required for attributing content such as posts or articles.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.