Inly Zapier API V1

Name: Inly Zapier API V1 API
Brand: Inly Zapier API V1
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey13 EndpointsREST

For Agents

Create and update Inly clients and projects, fetch sample records for automations, and subscribe to webhook events for clients, projects, payments, and contact form responses.

Install Jentic One Beta

Connect the Inly Zapier API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Inly Zapier API V1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Inly Zapier API V1 API.

Create new clients in Inly with structured contact and company fields via POST /zapier/actions/create_client

Create new projects under existing clients with POST /zapier/actions/create_project

Update existing clients and projects with POST /zapier/actions/update_client and update_project

GET STARTED

Start building with Inly Zapier API V1 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Inly Zapier API V1, keeping it validated and agent-ready. Inly is a small-business CRM and project workspace; the Zapier-facing API V1 exposes the integration surface used by automations to create and update clients and projects, fetch sample records for trigger configuration, and subscribe to webhook events. The 13 endpoints cover client and project create/update actions, profile and sample data reads (clients, projects, events, flows, contact form responses, payments), and webhook subscribe/unsubscribe.

Use Cases

Patterns agents use Inly Zapier API V1 API for, with concrete tasks.

★ Lead-to-Client Automation

When a new lead arrives from a website form, ad campaign, or third-party tool, automatically create a matching client record in Inly. POST /zapier/actions/create_client accepts the contact and company fields and returns the new client ID. Saves manual data entry for solo operators and small agencies whose CRM lives in Inly.

POST /zapier/actions/create_client with name, email, phone, and company fields from a new website lead, then return the resulting client ID.

Project Lifecycle Tracking via Webhooks

Subscribe to Inly webhook events so external systems are notified when projects, payments, or contact form responses are created or updated. POST /zapier/webhooks/subscribe registers the target URL and event type; POST /zapier/webhooks/unsubscribe removes it. Useful for keeping an external dashboard or accounting system in sync with Inly without polling.

Subscribe a webhook to the 'payment.created' event with target URL https://example.com/hooks/inly-payment via POST /zapier/webhooks/subscribe.

Cross-Tool Sync of Clients and Projects

Keep client and project records consistent between Inly and adjacent tools (accounting, scheduling, support). POST /zapier/actions/update_client and update_project let an integration apply changes from another system back into Inly when the source of truth lives elsewhere. Sample endpoints provide reference records during automation setup.

POST /zapier/actions/update_project with project_id and a new status of 'completed' to reflect a closed project from an external scheduling tool.

AI Agent for Solo Operators

An LLM agent acting as a virtual assistant for a freelancer or small agency uses Inly as its CRM tool — creating clients from inbound emails, opening projects when work is agreed, and updating records as conversations progress. Through Jentic, the agent searches by intent and executes against Inly without managing the API key directly.

Parse an incoming email from a prospect, then POST /zapier/actions/create_client with the extracted name, email, and company, followed by POST /zapier/actions/create_project for the discussed engagement.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for inly zapier api v1, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/zapier/actions/create_client

Create a new client

POST

/zapier/actions/create_project

Create a new project under a client

POST

/zapier/actions/update_client

Update an existing client

POST

/zapier/actions/update_project

Update an existing project

GET

/zapier/profile

Get the authenticated business profile

POST

/zapier/webhooks/subscribe

Subscribe to a webhook event

POST

/zapier/webhooks/unsubscribe

Unsubscribe from a webhook event

POST

/zapier/actions/create_client

Create a new client

POST

/zapier/actions/create_project

Create a new project under a client

POST

/zapier/actions/update_client

Update an existing client

POST

/zapier/actions/update_project

Update an existing project

GET

/zapier/profile

Get the authenticated business profile

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Inly X-API-KEY is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents call Inly operations through scoped Jentic credentials and never hold the raw key, which is critical for an API that can create or modify CRM records.

Intent-based discovery

Agents search Jentic with intents like 'create a client in Inly' or 'subscribe to a webhook' and Jentic returns the matching Inly operations with their input schemas — no need to read the Zapier-style endpoint docs.

Time to first call

Direct Inly Zapier API integration: a few hours to wire up the API key, action shapes, and webhook subscription flow. Through Jentic: minutes — search, load schema, execute.

FAQs

Specific to using Inly Zapier API V1 API through Jentic.

Why is there no official OpenAPI spec for Inly Zapier API V1?

Inly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Inly Zapier API V1 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Inly Zapier API V1 use?

The Inly Zapier API V1 uses an API key in the 'X-API-KEY' header on every request. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at runtime so the agent never sees the raw value.

Can I create projects under an existing client?

Yes. POST /zapier/actions/create_project accepts a client identifier alongside the project fields, so the new project is associated with the right client at creation time.

What are the rate limits for the Inly Zapier API V1?

Rate limits are not encoded in the spec; they are enforced per API key on the Inly side. Contact Inly support via api.inly.com for the current per-minute and per-day limits applied to your account.

How do I subscribe to Inly webhook events through Jentic?

Search Jentic for 'subscribe to an Inly webhook' to find POST /zapier/webhooks/subscribe. Load the schema, supply the event type and target URL, and execute. Use POST /zapier/webhooks/unsubscribe to remove the subscription. Get started at https://app.jentic.com/sign-up.

Why are there 'samples' endpoints in the API?

The /zapier/samples/* endpoints return representative records for clients, projects, events, flows, contact-form responses, and payments. Zapier-style automation builders use them to render field pickers when configuring triggers; agents can use them to discover the shape of records before constructing real updates.

Inly Zapier API V1

Connect the Inly Zapier API V1 to your agent

Capabilities

Start building with Inly Zapier API V1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs