You will be sent back to OAuth & Permissions where now appears a Bot User Auth Token.

Click on Allow button so Slack to confirm.

Click on Install on workspace button under OAuth Tokens for Your Workspace.

Click on OAuth & Permissions in the sidebar.

Send an email to any user at your domain.Now we need to configure an access token to communicate Slack and YepCode and add some permissions to the bot Configure OAuth and Permissions.

Go to SES Email receiving to make the rule set active.

When CloudFormation creates a SES receiving rule set, it’s inactive by default.

pCreateRuleSet and pCreateBucket - Should this stack create the resource or re-use an existing one.

pSlackWebhookSecret - Secret you created above.

pSlackChannel - I’m 80% sure this isn’t needed.

There can only be one active RuleSet in an account/region pDeliveryBucketName: Bucket you created above.Create an SecretsManager Secret for the Webhook.Add the following as an MX Record to your Route53 Hosted Zone:.Configure MX Records for the domain and verified identity.You’ll want to do this in the same account that has the Route53 Public HostedZone for the subdomain. Enter the domain you want to accept all email for.Go to the SES Console and Click on Configuration Verified Identities.We need to create and verify the domain in SES artisanally, then we do the rest via CloudFormation. Unlike every AWS walk through, I’m going to assume you have an AWS account and reasonably know what your doing.

What I created is a simple CloudFormation Template and Lambda that will take any inbound email to a Cloud Identity Domain, and forward it as a message to a Slack channel. A domain can’t be both it’s own Cloud Identity domain, and a User Alias Domain. However, for these Google Cloud Identity domains I couldn’t do that. My normal process for getting emails on secondary domains I own was to add them as a User Alias Domain attached to. As part of my work setting up free domains in Google, I realized I needed a way to receive email.

Forward email to slack