The Social Capital API
Village currently provides 10 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Get Person Paths
Returns connection paths and warmth score to a LinkedIn profile
Sort People
Sort a list of LinkedIn profiles by relationship strength with the user
Enrich Email
Enrich a single LinkedIn profile or Village ID with an email address
Enrich Profile
Enrich a single person profile with basic professional information and work history
Enrich Profile - Bulk
Enrich multiple person profiles (max 10) with basic professional information and work history.
Enrich Emails (Bulk)
Enrich multiple LinkedIn profiles or Village IDs with email addresses
Get Company Paths
Returns connection paths to a company using either its LinkedIn URL or domain URL
Sort Companies
Sort a list of companies by relationship strength with the user
Enrich Company
Enrich a single company profile with basic information including employee size, industry, and founding details
Enrich Company - Bulk
Enrich multiple company profiles (max 10) with basic information including employee size, industry, and founding details.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Use a change in Coherence to run a supported Village action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Get Person Paths
Combine Village with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
A Coherence workflow starts
Finishes with
Get Person Paths, then preserve the outcome in Coherence
The exact authentication fields depend on Village. The workflow structure stays straightforward:
Authorize the Village account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Village or provide a complementary trigger or action.
Village currently provides 10 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Village currently lists 0 triggers and 10 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Village triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
