Splunk SOAR

Phantom Add Artifact Error - source_data_identifier

linuts
Engager

Hello, whenever I try to add a new artifact I got the following error

phantom.act(): 'add_artifact_1' cannot be run on asset 'phantom helper'. The "add artifact" action requires the following parameters: source_data_identifier. The given parameters look like they were automatically generated by phantom.act() because an empty parameters list was passed to phantom.act(). The parameters list may have been empty because the preceding call to phantom.collect2() returned an empty list. Check your calling code in the action that generated this error

 

I presume is the container identifier, but how could I reference it in the playbook?

 

Labels (2)
0 Karma
1 Solution

phanTom
SplunkTrust
SplunkTrust

@linuts the source_data_identifier has to be set for each artifact and completely unique for each too. This may be done best by writing out the api yourself as according to the docs, a none entry for the identifier field will generate one for you, not sure why the app doesn't do it (https://docs.splunk.com/Documentation/Phantom/4.9/PlaybookAPI/ContainerAPI#add_artifact). If you set the container:id as the identifier you will be allowed to add 1 artifact to that container before you get an error as the identifier is already in use. 

-- Hope this helps, if so consider leaving some Karma. Even better is if this fixed your issue, that you mark as a solution for others to find. Happy SOARing!! ---

View solution in original post

phanTom
SplunkTrust
SplunkTrust

@linuts the source_data_identifier has to be set for each artifact and completely unique for each too. This may be done best by writing out the api yourself as according to the docs, a none entry for the identifier field will generate one for you, not sure why the app doesn't do it (https://docs.splunk.com/Documentation/Phantom/4.9/PlaybookAPI/ContainerAPI#add_artifact). If you set the container:id as the identifier you will be allowed to add 1 artifact to that container before you get an error as the identifier is already in use. 

-- Hope this helps, if so consider leaving some Karma. Even better is if this fixed your issue, that you mark as a solution for others to find. Happy SOARing!! ---
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...