Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Close

Sales automation and CRM integration for Close

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Close with Flows360

Sales automation and CRM integration for Close

Use the Close 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 6 actions and 3 triggers.

Available actions

  • Create Lead
  • Create Contact
  • Find Lead
  • Create Opportunity
  • Find Contact
  • Custom API Call

Available triggers

  • New Lead Created
  • New Contact Added
  • New Opportunity Added

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: Close
  • Package: @activepieces/piece-close@0.2.0
  • Exact artifact digest: sha256:722d74a654e51f148c15c5cd33cf01b15b01a509226ed8be36851b14718ce34d
  • 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

  • Create Lead (create_lead), Creates a new lead. Classification: read.
  • Create Contact (create_contact), Creates a new contact. Classification: read.
  • Find Lead (find_lead), Search for leads with advanced filtering options Classification: read.
  • Create Opportunity (create_opportunity), Create a new opportunity. Classification: read.
  • Find Contact (find_contact), Search for contacts by name, email, or other criteria with advanced filtering Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Lead Created, webhook.
  • New Contact Added, webhook.
  • New Opportunity Added, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects9
Supported actions6
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Lead Yes No Creates a new lead.
Create Contact Yes No Creates a new contact.
Find Lead Yes No Search for leads with advanced filtering options
Create Opportunity Yes No Create a new opportunity.
Find Contact Yes No Search for contacts by name, email, or other criteria with advanced filtering
Custom API Call Yes No Make a custom API call to a specific endpoint
New Lead Created Yes No webhook trigger declared by the pinned package.
New Contact Added Yes No webhook trigger declared by the pinned package.
New Opportunity Added Yes No webhook trigger declared by the pinned package.

Supported actions

Create Lead · Read

Creates a new lead.

create_lead · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the lead/company.
  • url · string · Optional
  • description · string · Optional
  • contacts · array · Optional, Array of contact details for this lead
  • statusId · string · Optional
  • customFields · object · Optional
Create Contact · Read

Creates a new contact.

create_contact · Risk: low · Retry: safe

Inputs

  • lead_id · string · Optional
  • name · string · Required
  • title · string · Optional
  • officePhone · string · Optional
  • mobilePhone · string · Optional
  • homePhone · string · Optional
  • directPhone · string · Optional
  • faxPhone · string · Optional
  • otherPhone · string · Optional
  • officeEmail · string · Optional
  • homeEmail · string · Optional
  • directEmail · string · Optional
  • otherEmail · string · Optional
  • url · string · Optional
  • customFields · object · Optional
Find Lead · Read

Search for leads with advanced filtering options

find_lead · Risk: low · Retry: safe

Inputs

  • search_type · string · Required
  • search_query · string · Required
  • match_type · string · Optional
Create Opportunity · Read

Create a new opportunity.

create_opportunity · Risk: low · Retry: safe

Inputs

  • lead_id · string · Optional
  • status_id · string · Required
  • name · string · Optional, A descriptive name for the opportunity.
  • note · string · Optional, Additional details about the opportunity.
  • confidence · number · Optional, The probability of winning this opportunity (0-100).
  • value · number · Optional
  • value_period · string · Optional, The period for the opportunity value.
  • contact_id · string · Optional, The ID of the contact associated with this opportunity.
  • user_id · string · Optional
  • custom_fields · object · Optional
Find Contact · Read

Search for contacts by name, email, or other criteria with advanced filtering

find_contact · Risk: low · Retry: safe

Inputs

  • search_type · string · Required
  • search_query · string · Required
  • match_type · string · Optional
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Lead Created · Webhook

Triggers when a new lead is created.

New Contact Added · Webhook

Triggers when a new contact is created.

New Opportunity Added · Webhook

Triggers when a new opportunity is created.

Setup

Setup

  1. Add the Close 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-close@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 3 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 Close 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-close@0.2.0 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