Availability and purpose

Important: The Claude/ChatGPT AI connector is not available yet. This workflow applies once the connector is turned on and you have a valid connection. The upload page is not a way to activate the connector.

Use Upload photos and videos at /connector-upload to put files from your device into the LeadKnight workspace your connected app uses. After upload, return to Claude or ChatGPT so it can discover and use the staged media through the connector. Uploading alone does not create a campaign, attach a file to a post, authorize publication or send anything to recipients.

This is different from uploading directly through the Developer API, which uses a server-side bearer key and a multipart request. Do not paste an API key into this page or into the host conversation.

Before you start

After the connector becomes available, finish AI connector setup and consent. Know which workspace was selected for the connection.
Sign in to LeadKnight with a current member of that workspace and have permission to upload media. An upload link is not permission to enter a workspace you do not belong to.
Ask the connected app for an upload link for your photos/videos. Use the link it provides so the intended workspace is included.
Keep the original files on your device. This is temporary staging for content creation, not a file backup or permanent hosting service.
Choose supported real image/video content, within the limits below after any image preparation. You must have permission to use the media.

Open the correct workspace

Open the link from Claude or ChatGPT. The app route is /connector-upload; a supplied workspace query parameter identifies its requested workspace.
Wait while Opening your workspace… appears. If the requested workspace differs from the currently selected one, the page attempts to switch before accepting files.
If Couldn't open that workspace. appears, select Try again. Do not start another upload in a different workspace as a workaround.
If You're not a member of that workspace. appears, check the signed-in account and current membership. The page refuses invalid workspace IDs and workspaces not available to your identity.
Once Upload photos and videos is ready, check the workspace in the app shell before selecting files. If the URL has no workspace parameter, the page uses your current workspace rather than choosing the connector's binding for you.

Changing the active workspace in the web app does not change the workspace selected for an existing AI connection. If they differ, use the upload link for the connection's workspace or reconnect deliberately through consent. Do not alter query parameters to try to bypass access restrictions.

Choose files and follow the results

Under Drop photos or videos here, or choose files., drag files into the drop area or use Choose files. You can select multiple files in one batch.
A row appears for each selected file, showing its name and Waiting. The batch is processed one file at a time; the current row changes to Uploading….
If an image needs additional preparation, follow the compression decision described below. A skipped or failed file does not prevent later files in that batch from being attempted.
Watch each row for Uploaded, Upload failed or Skipped. Failed rows include a localized explanation when one is available. Do not assume all files succeeded because one row is uploaded.
Wait until the current batch is finished. Choose files is disabled while it is running; do not drop another batch during the upload. Once finished, you can choose another batch if needed.
When at least one file succeeded and processing has finished, a completion message states the number uploaded and asks you to return to Claude or ChatGPT and say done. The count reflects successful files still listed on this page, not failed/skipped files.
Return to the same host conversation and say done. Ask the app to use the uploaded files for the intended task. The page does not automatically navigate back or show asset IDs for manual copying.
Before any consequential action, review the requested content, account, destination and schedule. Upload completion itself is not permission to publish.

File selection starts the upload workflow; there is no separate final upload or publish button. Keep the page open while processing. Do not reload it just to clear a waiting row, because the visible list is not a durable upload history.

What each status means

Status	Meaning	What to do
Waiting	The selected file has not reached its turn.	Wait while earlier files finish.
Uploading…	The file is being prepared or uploaded; preparation can include a compression dialog.	Keep the page open and answer any visible preparation question.
Uploaded	The upload request succeeded for that file.	Let the batch finish, then return to the connected app.
Upload failed	Unsupported content, preparation refusal, server or connection failure.	Read the row's message, correct the cause and select the intended file again if appropriate.
Skipped	Image preparation was declined/cancelled.	Select it again only if you want to approve preparation or supply a different version.

Formats, sizes and image preparation

File	Supported handling and limit
JPEG, PNG, WebP, GIF	Stored image formats; each uploaded image must fit within 10 MiB. Supported images already within the limit are sent as selected.
Other image formats	The browser attempts conversion to a stored format if it can open the image. This is not a promise that every browser can open HEIC, HEIF, AVIF or every image file.
MP4 video	Up to 256 MiB. Larger videos are refused before upload; this page does not compress video.
Other videos or non-media files	The broad file-picker filter is not a guarantee of support. The supported video MIME is `video/mp4`; documents, audio-only files and unsupported video types are not accepted by this workflow.

Automatic preparation

Oversized still images are re-saved on your device at reduced size/quality until they fit, when possible. A converted image can also have a different filename extension. If an unstored format can be opened by the browser, it is converted even if its original size was small. Conversion of animated AVIF keeps its first frame; do not rely on that format to preserve motion.

If an image cannot be opened, save a copy as JPG or PNG and select that copy. A file extension or MIME label alone does not guarantee that the server accepts the actual file content.

Manual compression or skipping

If automatic preparation cannot fit a photo, The image is too big offers Compress manually or Skip this image. Manual compression can visibly reduce quality. For an oversized GIF, a warning explains that the animation will be lost and only its first frame is retained.

Read the filename, current size, upload limit and any animation warning.
Select Compress manually only if the quality/motion trade-off is acceptable. The prepared file continues to upload if it fits.
Select Skip this image, or dismiss the preparation question, to leave that file unuploaded. Its row becomes Skipped, and processing continues with the next file.
If even the stronger compression cannot fit the image, supply a smaller suitable copy instead of repeatedly selecting the same unmodified file.

Keep your original if image fidelity or animation matters. A converted/uploaded still is not a replacement for the source video or animated image.

Workspace changes, uncertain results and temporary storage

The visible file list and counters reset when the active identity or workspace changes. The page stops continuing the old batch in the newly selected scope and does not send a prepared file into a different workspace after a preparation dialog. A request already in flight may already have stored a file in its original workspace; a cleared list does not prove it was cancelled or deleted.

If you lose the completion screen or a network failure leaves an upload's outcome uncertain, return to the same connected workspace and ask the host to inspect available media before uploading again. Uploads have no exactly-once guarantee; repeating a file can create another asset. There is no per-row retry control: selecting a file again starts a new attempt.

The completion message warns that files not used within 24 hours are removed. Treat that as temporary staging: unused files become eligible for cleanup after 24 hours, not a promise of deletion at the exact second. Ask the app to use/attach them promptly. Upload success alone does not attach the file to a campaign, and temporary media URLs are not permanent publication URLs.

If something goes wrong

Symptom	Likely cause	What to do
The connector cannot provide a usable journey	The AI connector is not available yet or not connected.	Wait for availability and complete connector consent; this upload page does not bypass it.
Membership error	Wrong signed-in account, invalid workspace parameter or membership removed.	Use the right account and a workspace you currently belong to; request a fresh link from the intended connection.
Workspace keeps opening or switching fails	The app has not reached the requested workspace.	Wait for readiness or select Try again after the switch error. Do not select files in a different workspace.
Unsupported file message	The item is not a recognized image or MP4 video.	Supply a supported real media file; renaming an extension is not conversion.
HEIC/other image cannot be opened	This browser cannot decode it.	Save/export as JPG or PNG and upload the copy.
Photo too large after preparation	Compression could not fit it or was declined.	Use an appropriate smaller copy or deliberately approve the compression trade-off.
Large video refused	The video exceeds 256 MiB.	Export a smaller MP4 outside this page, then select it.
Some files succeed and others fail	Per-file results are independent.	Keep successes; correct only failed/skipped files instead of repeating the whole batch.
Upload count/list disappears	Identity/workspace changed or page was reloaded.	Check media in the original workspace before uploading again; the list is not permanent history.
Host cannot find uploaded files	Wrong workspace binding, no completed upload or unused staging expired.	Check the Uploaded rows and connection workspace, tell the host you are done, and inspect current media before retrying.
Concern about accidental publication	Uploads stage media only, but later connector actions can act immediately.	Review the next instruction in the host; do not ask it to publish until content and destinations are confirmed.