Integration
Connect Hjarni to SignRequest
When New Note fires in Hjarni, your agent runs Add document in SignRequest. 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 SignRequest 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 SignRequest
When New Note in Hjarni
then Add document in SignRequest
When New Note in Hjarni
then Add document attachment in SignRequest
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 SignRequest
Triggers and actions 1 trigger · 26 actions
Trigger
New NoteTriggers when a new note is created.
Action
Add File to NoteAttaches a file to an existing note from a URL.
Action
Add tagCreate a tag.
Action
Create FolderCreates a new folder with a name, parent folder, description, and AI instructions.
Action
Create NoteCreates a new note with a title, body, tags, and folder.
Action
Delete folderDelete a container.
Action
Delete noteDelete a note (moves to trash).
Action
Delete tagDelete a tag.
Action
Get folderFetch one container by id.
Action
Get noteFetch one note by id with body, tags, container, files.
Action
List notesList notes, filter by scope/container_id/tag, paginated.
Action
List tagsList tags.
Action
Update folderUpdate a container.
Action
Update noteUpdate note fields (title, body, tags, container, append_body etc, expected_lock_version).
Action
Update tagRename/update a tag.
Action
Add documentCreates a document in SignRequest from a file link, uploaded file content or a template, ready to be sent out for signature.
Action
Add document attachmentAttaches a file to an existing SignRequest document, from a public link or from the file's contents.
Action
Cancel SignRequestCancels a SignRequest that is still pending, so its signers can no longer sign the document.
Action
Delete documentDeletes a document from your SignRequest team.
Action
Get documentReturns a single SignRequest document by its ID, including its status, signers, and temporary links to the original and signed PDFs.
Action
Get SignRequestReturns a SignRequest by its ID, including its signers and their signing status, the email subject and message, and the linked document.
Action
List documentsReturns the documents in your SignRequest team, optionally filtered by status, external ID, sender, owner or date.
Action
List SignRequestsReturns the signature requests in your SignRequest team, optionally filtered by sender email or by who signs.
Action
List templatesReturns the templates available to your SignRequest team, with each template's name, ID and signer setup.
Action
Resend SignRequestResends the signature request email to the signers of an existing SignRequest who have not yet signed.
Action
Send SignRequestSends an existing SignRequest document out for signature to one or more signers, and returns the new SignRequest.
Action
Send SignRequest From TemplateCreates a document from one of your SignRequest templates and sends it to the signers you choose in a single step. Returns the new SignRequest with its signers and document.
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 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.
Hjarni to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into SignRequest
HubSpot to SignRequestHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SignRequestSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SignRequestSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SignRequestGoogle Sheets
Gmail to SignRequestGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignRequestGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hjarni and SignRequest, 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 SignRequest when something happens in Hjarni?
Any of SignRequest's 12 actions, including Send SignRequest, Send SignRequest From Template, Add document and Add document attachment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SignRequest to Hjarni?
SignRequest has no triggers in the catalog today, so automations start in Hjarni. If you need the other direction, ask: your agent reads SignRequest's API documentation and adds it.
Do I have to build a connector for Hjarni or SignRequest?
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 SignRequest 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.