We'll send you an email when the integration is ready and keep you informed on all the latest Connect updates.
MoonClerk lets anyone accept recurring payments and one-time payments quickly and easily without any coding.
Intercom is a customer communication platform built for business, used by many businesses from small start-ups to global enterprises. It enables targeted communication with customers on your website, inside your web and mobile apps, and by e-mail.
Intercom IntegrationsIntercom + MailChimp
Remove users from Mailchimp as soon as they unsubscribe from Intercom Read More...It's easy to connect moonclerk + Intercom without coding knowledge. Start creating your own business flow.
Triggers when a payment has been made on MoonClerk.
Triggers when a payer checks out and creates a Recurring Plan in MoonClerk.
Triggers when a new conversation is created by a user in Intercom.
Triggers when a new Lead is created.
Triggers when a new user is created.
Create or update an Intercom lead. If an ID is provided, the lead will be updated.
Update a user within Intercom given their e-mail address.
Send a message from a user into your Intercom app. Note: you must have a valid plan on Intercom to access this action.
(30 seconds)
(10 seconds)
(30 seconds)
(10 seconds)
(2 minutes)
Moonclerk allows one to send messages via Intercom to a specified email address. Let’s say, we want to receive Intercom messages and send to a specified email address then we need to do something like this:
Create a new application in Intercom and get the application id and app secret, we will need these later in the integration.
Then you need to add moonclerk_webhook (https://github.com/moonclerk/moonclerk-webhook. as a webhook listener in your Rails app. The fplowing code snippet shows how you can add moonclerk_webhook in your Rails App:
# config/initializers/moonclerk_webhook.rb require 'moonclerk_webhook' MoonclerkWebhook.configure do |config| config.id = 'your application id' config.secret = 'your app secret' end
Now we need to create a new contrpler for sending messages via Intercom. Let’s name it email_contrpler . To do that lets fplow the below steps:
rails generate contrpler email index show edit update destroy reply_to_message action_mailer_mailer default_url_options root to. 'email#destroy' #contrpler def index mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail.subject = "Intercom Email #{email['name']}" mail.greeting = "Hi #{email['name']}, We have some important information for you." mail end def show @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end end def edit @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def update @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def destroy @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def reply_to_message @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end
Here, we are creating an object of ActionMailer::Message which will be used to send emails using our application configuration. You can find more information about ActionMailer here (http://guides.rubyonrails.org/action_mailer_basics.html. Now, create an action in the contrpler named reply_to_message . This action will be used when you reply to an existing message in Intercom (https://www.intercom.io/docs/messages/. If you try to access this action without parameters it will redirect you to the default route which is ‘/’ (in Rails apps.
Now set up cron jobs using the fplowing command (in rails):
bundle exec moonclerk -c /path/to/moonclerk/config/application_specific_configuration.yml -r /path/to/moonclerk/bin/moonclerk -e production -o /path/to/rails/app -f /path/to/moonclerk/logs/intercom_myapp_* -C /path/to/moonclerk/config/production_configuration.yml
You may need a cron job if you want to trigger a digest cycle on a regular interval so that if any new events have been received they would get processed by the next digest cycle. This is not required if there are no new events available since log entries can be triggered by new events even on a daily basis without setting up a cron job for this purpose. Once you get all the necessary integration done then your code will look something like this:
require 'moonclerk' MoonclerkWebhook.configure do |config| config.id = 'your application id' config.secret = 'your app secret' end # contrpler def index mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def show @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def edit @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def update @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def destroy @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end def reply_to_message @email = IntercomEmail.find(params[:id]. mail = ActionMailer::Message.new email = IntercomEmail.find(params[:id]. mail << email mail end # config/initializers/moonclerk_webhook.rb require 'moonclerk' MoonclerkWebhook.configure do |config| config.id = 'your application id' config.secret = 'your app secret' end # config/environments/production-local-config-customization-example-site-application-specific-configuration-sample-app-configuration-sample-app-production-local-config-customization-example-site-application-specific-configuration-sample-app-production-local-config-customization-example-site-production-local-config-customization-example-site-production require 'base64' require 'json' class ApplicationSpecificConfig < MoonClerk :. Config include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration :. SendRecipientsConfig include Moonclerk :. WebHook :. Configuration -> RecipientUrlOptions include Moonclerk :. WebHook -> RecipientUrlOptions
The process to integrate 403 Forbidden and 403 Forbidden may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.