Files didn't upload to Salesforce from a project automation
Updated
Applies to: Super Admins, Creators, and Integrators, with Salesforce connected
Files from a task didn't reach the Salesforce record. We'll check the automation's trigger first, and then its row in Logs.
Why it happens
Upload Files to Salesforce Object uploads files only when its automation's trigger is Task completed. With any other trigger, it uploads nothing, even if Logs shows a check mark for it. That includes Any task completed and Subtask completed.
With a Task completed trigger, it sends the files uploaded on that task through a File Upload subtask or a form's Request Files field. Files shared through Share Files, and links, aren't sent. The files go to the record selected in Salesforce Object Entity.
The upload runs in the background after the task is completed, so its row appears in Logs only after the upload has run.
Fix it
To start, select the automation on the project's Automations tab. Its first step is the trigger.
If the trigger isn't Task completed
Select Create.
For the trigger, select Task completed.
In Task, select the task that has the files.
In the new Action step, select Upload Files to Salesforce Object.
In Salesforce Object Entity, select the record.
Select Create.
Optional: In the old automation, remove the upload step with its trash button, and then select Save. If that was its only action, select Delete Rule and then Confirm instead.
If the automation came from a playbook or the Automations Library, change its trigger there too. Otherwise, new projects get the same trigger. Understanding Playbook & Project Automations explains where each one is edited.
If the trigger is Task completed
Select Logs.
Select Refresh. The row can take a moment to appear.
Find the
uploadFilesToSalesforceObjectrow. On this row, User is the person who completed the task, or the automation's creator when that isn't known. If there's no row, follow Project automation didn't run or failed.If Success shows a check mark, check that the files were uploaded through a File Upload subtask or a form's Request Files field on the trigger's task.
If Success shows a failure, check that the trigger's task isn't archived. Upload rows don't show a View button, so the error message isn't visible here.
Select Workflow.
Select the Upload Files to Salesforce Object step.
Check that Salesforce Object Entity shows the record you expected and that the record still exists. If you see
Selected integration entity not found. Please select one below., select the record.If you changed the record, select Save.
If the row still shows a failure, check that the Salesforce integration user can create files on that Salesforce object. Configure Salesforce Permissions for OnRamp Project Automation covers the permissions it needs.
Warning: Completing the task again runs the upload again. Files that already reached Salesforce can be uploaded a second time.
Still stuck?
Contact support with the project's name and link, the task's name, the Salesforce record you expected, the names of the missing files, and the row's Timestamp, even if the row has no View button.