Use workflow property in custom action

Develop, Build & Integrate APIs & Integrations
1

I’m trying to create a custom workflow action which requires a file as an input field. I know that it’s possible to use a contact property of file type, for example. But in my case this file always needs to be the same for any workflow execution.

I found that I can create a workflow property of file type. And now I wonder if it’s possible to access workflow property value somehow from the action?

If I’ll create an input field definition like the following, it allows me to select only contact properties, but not from the workflow.

{
 "typeDefinition": {
 "name": "fileId",
 "type": "string",
 "fieldType": "file",
 "options": [],
 "optionsUrl": null,
 "referencedObjectType": null,
 "externalOptions": false,
 "externalOptionsReferenceType": null
 },
 "supportedValueTypes": [
 "OBJECT_PROPERTY"
 ],
 "isRequired": false,
 "automationFieldType": null
}

P.S. I don’t want to add an input field where my customers need to write an ID of the file by their own.

2

Hi @kronst,
Thank you for reaching out to the Community and for sharing the code with us!
I’d be happy to put you in touch wit our Top Experts for this: Hi @HFisher7, @miljkovicmisa and @ChristinaKay do you have suggestions to help @kronst, please?

Thank you very much and have a wonderful day!
Best,
Bérangère

3

@kronst - If I am understanding correctly, based on your saying “But in my case this file always needs to be the same for any workflow execution.” instead of using a personalisation token pulling a value from a CRM property into the code can you not use the file URL in the cosed instead, so it is the same across all workflow enrollments?

4

Hello, @HFisher7!

As a result I just want to create a custom action where user could select a file that will be used in an action execution. But I like the idea of approach when customer specifies the direct link to a file. :thinking: This could even reduce the complexity of execution implementation. I’ll discuss this point with my team.

Thanks a lot for the reply, Hannah.