f127425806
* Initial commit * Files moved in certified-connectors * Added missing description and x-ms-summary props * Added contact and x-ms-connector-metadata * Updated response name * Added whitlisted redirect url * Changed categories * Changed icon brand color * Added missing response types * Updated apiProperties.json and apiDefinition.swagger.json (#546) * Update apiDefinition.swagger.json * Add files via upload * update readme * Update Get User Info Action and apiProperties file * In d insurance (#560) * Create IN-D KYC India * Delete IN-D KYC India * Create apiDefinition.swagger.json * Add files via upload * Create README.MD * Update README.MD * Delete README.MD * Delete apiDefinition.swagger.json * Delete apiProperties.json * Create IN-D Insurance * Delete IN-D Insurance * Create IN-D Insurance * Delete IN-D Insurance * Create Readme.md * Add files via upload * Add files via upload * Delete Readme.md * Delete apiDefinition.swagger.json * Delete apiProperties.json * Create Readme.md * Add files via upload * Add files via upload * Updated clientId * Updated summaries for triggers * Added intro.md * update - descriptions formated as html * updated redirectUrl * hidden clientId * Removed intro.md from app * Adapted titles and summaries * Tweaked x-ms-summary values Co-authored-by: Denis Šišić <denis.sisic@gmail.com> Co-authored-by: Calvin Leong <60145424+calvinleong@users.noreply.github.com> Co-authored-by: gowthamd3 <65020517+gowthamd3@users.noreply.github.com> |
||
---|---|---|
.. | ||
Readme.md | ||
apiDefinition.swagger.json | ||
apiProperties.json |
Readme.md
Evocom Connector
The Evocom Connector builds the bridge between the easiest solution for collaborative processes and the Microsoft Power Platform (and Azure Logic Apps). According to the motto "first digitize, then automate", companies transform manual processes into digital processes in order to further integrate and automate them afterwards.
Prerequisites
You will need the following to proceed:
- An Evocom Productivity subscription
- A Microsoft Power Apps or Power Automate plan
Set up an Evocom account
https://productivity.evocom.net/
Supported Operations
The connector supports the following operations:
Actions
Create task
: This operation is used to create a new task/approval/request in you task managerEdit task
: This operation is used to edit a task, which wasn´t created by a process instanceGet process
: This operation retrieves process by IDGet processes
: This operation retrieves all processes to which you are entitledGet task
: This operation retrieves task by IDGet tasks
: This operation retrieves all tasks to which you are entitledGet teams
: This operation retrieves all teamsGet template
: This operation retrieves process template by IDGet template steps
: This operation retrieves the list of steps defined in templateGet templates
: This operation retrieves all process templatesStart process
: This operation is used to start a process. Fields are dynamic from the start form of the process template.Get user
: This operation retrieves user by EP login (email) or Azure user id
Trigger
New process
: Triggers when a new process is started.Changed process
: Triggers when process steps change or process is completed.New task
: Triggers when a new task is created.Changed task
: Triggers when something has changed in a task.New team
: Triggers when a new team is created.Changed team
: Triggers when something has changed in a team.
Known issues and limitations
- You cannot use files in actions and as dynamic content in Power Automate.