Integration
Connect Hjarni to Clicksign
When New Note fires in Hjarni, your agent runs Notifications Email in Clicksign. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Hjarni and Clicksign to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Hjarni can start in Clicksign
When New Note in Hjarni
then Notifications Email in Clicksign
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Hjarni and Clicksign
Triggers and actions 1 trigger · 25 actions
- New Note
Triggers when a new note is created.
- Add File to Note
Attaches a file to an existing note from a URL.
- Add tag
Create a tag.
- Create Folder
Creates a new folder with a name, parent folder, description, and AI instructions.
- Create Note
Creates a new note with a title, body, tags, and folder.
- Delete folder
Delete a container.
- Delete note
Delete a note (moves to trash).
- Delete tag
Delete a tag.
- Get folder
Fetch one container by id.
- Get note
Fetch one note by id with body, tags, container, files.
- List notes
List notes, filter by scope/container_id/tag, paginated.
- List tags
List tags.
- Update folder
Update a container.
- Update note
Update note fields (title, body, tags, container, append_body etc, expected_lock_version).
- Update tag
Rename/update a tag.
- Create Signer
Creates a signer on a Clicksign envelope and returns the new signer record, ready to be linked to the envelope's documents.
- Delete Document
Deletes a draft document from a Clicksign envelope.
- Delete Signer
Deletes a signer from an envelope, as long as the signer has not started signing.
- List Documents
Returns the documents in a Clicksign envelope, with each document's status, file name and download link.
- List Templates
Returns the document templates (modelos) in your Clicksign account.
- Notifications Email
Sends a signer a notification asking them to sign an envelope, with an optional custom message and email wording. Returns the notification and whether the signer was notified.
- Notifications SMS
Re-sends the signing notification to a signer of an envelope, delivered over the channel the signer is set up for (SMS for SMS signers), with an optional custom message.
- Notifications WhatsApp
Sends a reminder to a signer on an envelope through the WhatsApp channel configured for that signer, and returns whether the signer was notified.
- Remove Signer From Document
Removes a signer who has not yet started signing from a Clicksign envelope.
- View Document
Returns the current details and status of a document inside a Clicksign envelope.
- View Signer
Returns the current details of a signer on a Clicksign envelope, including name, email, phone number and notification preferences.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Hjarni
Hjarni to GroqGroq is a provider of fast LPUs and cloud tools to accelerate AI inference at scale and low cost.
Hjarni to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Hjarni to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hjarni to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hjarni to MailchimpMailchimp marketing automation and email platform.
Hjarni to StripeStripe is a payment processing platform for online businesses.
More into Clicksign
Google Sheets to ClicksignGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ClicksignGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ClicksignGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hjarni and Clicksign, answered
What can start an automation from Hjarni?
Any of Hjarni's 1 trigger in the catalog, including New Note. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Clicksign when something happens in Hjarni?
Any of Clicksign's 11 actions, including Create Signer, List Documents, List Templates and Notifications Email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clicksign to Hjarni?
Clicksign has no triggers in the catalog today, so automations start in Hjarni. If you need the other direction, ask: your agent reads Clicksign's API documentation and adds it.
Do I have to build a connector for Hjarni or Clicksign?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Hjarni and Clicksign without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.