Inhubber

Connect an Inhubber company to file contracts from a process. metamorphOS calls Inhubber to create a document, upload its files and make them accessible, and to read documents and custom field definitions back. Inhubber does not send anything to metamorphOS, so this connector is outbound only.

What you can do

• Create Document: create an Inhubber document in draft, owned by the connected user. Files are uploaded to it next.
• Upload File: upload one file to a document. You pass only the file; metamorphOS prepares the upload the way Inhubber requires. A file type can be set in the same step.
• Set File Type: set or change an uploaded file’s type: e_signature (to be signed in Inhubber), signed_offline (already signed) or other. A file can be opened in Inhubber only once it has a type.
• Get Document: read one document, including what the connected user may do with it.
• List Documents: list the documents the connected user can see, one page at a time, with search, state and owner filters.
• Get Custom Field Definitions: list the custom fields your company defined in Inhubber: text, options, date, number and payment fields.

Before you start

You need:

• An Inhubber company on the Professional tier. API access is part of that tier.
• A dedicated technical Inhubber user for metamorphOS, with an email address and password. Only a document’s owner may upload files to it or change their type, and the connector owns everything it creates, so use a user that exists for this purpose rather than a person’s account. To read documents that other members own, the user needs the company role ADMIN.

Set up Inhubber

1. Create the technical user in your Inhubber company and give it the role it needs (see above).
2. Sign in once as that user to confirm the email address and password work.
3. Note the email address and password. You enter them in metamorphOS in the next step.

Connect in metamorphOS

Activate the Inhubber connector from the marketplace and add a credential of type Username and password (login token):

• Username: the technical user’s email address.
• Password: the technical user’s password, as you type it into Inhubber.

Enter the password as it is. metamorphOS hashes it the way Inhubber’s login expects and exchanges it for a session token on each login; there is nothing to hash or convert yourself. When Inhubber ends a session, metamorphOS signs in again with the stored credential.

Check the setup

The Inhubber Upload Test process checks the connection end to end. It takes one file and:

1. creates a document titled metamorphOS upload test,
2. uploads the file to it,
3. sets the file’s type to other, so it can be opened,
4. reads the document back.

The new document appears in Inhubber under the technical user. Delete it there when you no longer need it.

Good to know

• Download links expire after one day. A file’s download link is valid for a day after it is issued. Read the document again for a fresh link instead of storing one.
• A file without a type stays in draft and cannot be opened. Set the type on upload or with Set File Type.
• Custom field values are read, not written. Documents come back with their custom field values, and Get Custom Field Definitions describes the fields. Writing a value is not part of the connector, because Inhubber documents it for single-line text fields only.
• No events from Inhubber. Inhubber documents no webhooks, so a process learns about a signature or a state change by reading the document again.