{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/acce7eb33b7048c6aa58b2da9bbfd1b7\" frameborder=\"0\" width=\"3170\" height=\"2377\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2377,"width":3170,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2377,"thumbnail_width":3170,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/acce7eb33b7048c6aa58b2da9bbfd1b7-00001.jpg","duration":199.32,"title":"Primer Automation: Demo use case end to end","description":"A step by step demo of creating workflows surrounding a specific use case: Identity verification. \n\nDon't forget to add the \"Continue payment flow\" action at 00:15!\n\nUse case requirements\n* Every time a user has made a payment with a new payment method, send them a verification link via email.\n* Capture the payment when the user is approved, and cancel if not. \n* Notify the team on Slack for specific verification outcomes, like \"fraud suspected\", or \"well known fraudster\".\n\nFor the sake of this demo, the following apps will be used to implement this use case:\n\n* Payments\n* Onfido for KYC\n* Mandrill to send an email\n* Slack to post a message"}