If you’re new to Unstructured, read this note first.
Before you can create a source connector, you must first sign in to your Unstructured account:
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.
After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.
You can also create source connectors with the Unstructured API. Learn how.
If you need help, reach out to the community on Slack, or contact us directly.
You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Confluence.
The requirements are as follows.
A Confluence Cloud account or Confluence Data Center installation.
The site URL for your Confluence Cloud account or Confluence Data Center installation.
A user in your Confluence Cloud account or Confluence Data Center installation.
The user must have the correct permissions in your Conflunce Cloud account or Confluence Data Center installation to access the target spaces and pages.
One of the following:
Optionally, the names of the specific spaces in the Confluence instance to access.
The following video provides related setup information for Confluence Cloud:
The source connector outputs any permissions information that it can find in the source location about the processed source documents and associates that information with each
corresponding element that is generated. This permissions information is output into the permissions_data
field, which is within the
data_source
field under the element’s metadata
field. This information lists the users or groups, if any, that have
permissions to read, update, or delete the element’s associated source document.
The following example shows what the output looks like. Ellipses indicate content that has been omitted from this example for brevity.
To look up information about a particular Confluence user, use the user’s ID (also known as their account ID) from the preceding output to call the GET /wiki/rest/api/user operation in the Confluence REST API.
To look up information about a particular Confluence group, use the group’s ID from the preceding output to call the GET /wiki/rest/api/group/by-id operation in the Confluence REST API.
To create the source connector:
Fill in the following fields:
luke,paul
.
By default, if no space names are specified, and the Max Number of Spaces is reached for the instance, be aware that you might get
unexpected results.If you’re new to Unstructured, read this note first.
Before you can create a source connector, you must first sign in to your Unstructured account:
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.
After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.
You can also create source connectors with the Unstructured API. Learn how.
If you need help, reach out to the community on Slack, or contact us directly.
You are now ready to start creating a source connector! Keep reading to learn how.
Ingest your files into Unstructured from Confluence.
The requirements are as follows.
A Confluence Cloud account or Confluence Data Center installation.
The site URL for your Confluence Cloud account or Confluence Data Center installation.
A user in your Confluence Cloud account or Confluence Data Center installation.
The user must have the correct permissions in your Conflunce Cloud account or Confluence Data Center installation to access the target spaces and pages.
One of the following:
Optionally, the names of the specific spaces in the Confluence instance to access.
The following video provides related setup information for Confluence Cloud:
The source connector outputs any permissions information that it can find in the source location about the processed source documents and associates that information with each
corresponding element that is generated. This permissions information is output into the permissions_data
field, which is within the
data_source
field under the element’s metadata
field. This information lists the users or groups, if any, that have
permissions to read, update, or delete the element’s associated source document.
The following example shows what the output looks like. Ellipses indicate content that has been omitted from this example for brevity.
To look up information about a particular Confluence user, use the user’s ID (also known as their account ID) from the preceding output to call the GET /wiki/rest/api/user operation in the Confluence REST API.
To look up information about a particular Confluence group, use the group’s ID from the preceding output to call the GET /wiki/rest/api/group/by-id operation in the Confluence REST API.
To create the source connector:
Fill in the following fields:
luke,paul
.
By default, if no space names are specified, and the Max Number of Spaces is reached for the instance, be aware that you might get
unexpected results.