Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Proxycurl

Enrich LinkedIn people and company profiles with Proxycurl.

CategorySales And Crm
Authenticationcustom
Version0.1.4
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Proxycurl with Flows360

Enrich LinkedIn people and company profiles with Proxycurl.

Use the Proxycurl connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

  • Get Person Profile
  • Get Company Profile
  • Search People
  • Lookup Person Email
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Proxycurl
  • Package: @activepieces/piece-proxycurl@0.1.4
  • Exact artifact digest: sha256:c9657ecaf5831379ea5ceeb5086f84e698e236ddba0086d6da4cdc26bd781335
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Person Profile (get_person_profile), Fetch a LinkedIn person profile from Proxycurl. Classification: read.
  • Get Company Profile (get_company_profile), Fetch a LinkedIn company profile from Proxycurl. Classification: read.
  • Search People (search_people), Search for people in Proxycurl using lightweight keyword filters. Classification: read.
  • Lookup Person Email (lookup_person_email), Lookup the work email address for a LinkedIn person profile. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to any Proxycurl endpoint. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Proxycurl API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Person Profile Yes No Fetch a LinkedIn person profile from Proxycurl.
Get Company Profile Yes No Fetch a LinkedIn company profile from Proxycurl.
Search People Yes No Search for people in Proxycurl using lightweight keyword filters.
Lookup Person Email Yes No Lookup the work email address for a LinkedIn person profile.
Custom API Call Yes No Make a custom API call to any Proxycurl endpoint.

Supported actions

Get Person Profile · Read

Fetch a LinkedIn person profile from Proxycurl.

get_person_profile · Risk: low · Retry: safe

Inputs

  • linkedin_profile_url · string · Required, Public LinkedIn profile URL, for example https://www.linkedin.com/in/williamhgates
Get Company Profile · Read

Fetch a LinkedIn company profile from Proxycurl.

get_company_profile · Risk: low · Retry: safe

Inputs

  • url · string · Required, LinkedIn company URL, for example https://www.linkedin.com/company/apple/
Search People · Read

Search for people in Proxycurl using lightweight keyword filters.

search_people · Risk: low · Retry: safe

Inputs

  • country · string · Optional, Optional country filter, for example us, gb, or sg.
  • headline · string · Optional, Optional keywords expected in the person headline.
  • summary_keywords · string · Optional, Optional keywords expected in the summary/about section.
Lookup Person Email · Read

Lookup the work email address for a LinkedIn person profile.

lookup_person_email · Risk: low · Retry: safe

Inputs

  • linkedin_profile_url · string · Required, Public LinkedIn profile URL to enrich.
  • callback_url · string · Optional, Optional webhook URL for async completion callbacks from Proxycurl.
Custom API Call · Read

Make a custom API call to any Proxycurl endpoint.

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Required, Authorization headers are injected automatically from your connection.
  • queryParams · object · Required
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional
  • timeout · number · Optional
  • followRedirects · boolean · Optional

Setup

Setup

  1. Add the Proxycurl connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-proxycurl@0.1.4; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Proxycurl connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-proxycurl@0.1.4 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com