Minimally maintained

English

amoCRM is a web service for your sales management. Thousands of businesses use amoCRM to manage their leads and pipeline. Just add your leads to amoCRM, and the system will ensure that no lead is ever forgotten.

AmoCRM module allows you to configure any reaction in Drupal, which module Rules and other related modules allow to implement, for each action in amoCRM (creating, editing and deleting of leads, contacts and companies, recover of leads, change the status of leads). For example, when you change the status of a lead a letter is sent to a site administrator.

Did you ever wanted to add a bean to a panel but you can't export a bean, don't want to have content on git and dont wan't to lose your modifications on panels in a feature revert? Then this module is for you!

The module provides a widget that works like a placeholder in panels, you add the module to a panel, input the Bean Label (it's called delta on database), and exports with features. It's just like if you were using a machine name in a bean, instead of depends on bean ids.

How to use:

When editing a panels page:

Install a feature module and disabled it.

Support some modules to rebuild feature:

• Field Group
• Profile2
• Quicktabs
• Views
• (CTools) Page Manager
• Field Permissions
• Password policy

This module creates entities for Australian postcodes.
It does this by importing from a csv file that is included in the module.
The information that it includes for each postcode is:
Postcode
Suburb
State
Delivery centre
Delivery centre type
Latitude
Longitude

As the module leverages the Entity API, it has views support for all fields.
There is currently 1 custom views filter for state (select options instead of an autocomplete).

8.x-1.x

This module provides the Stripe PHP library as a service. It provides:

• API key storage via Key.
• A "@stripe_api.stripe_api" service that can be injected into your PHP classes

Once you've enabled the module and set your API keys, you are free to use the Stripe API library in your custom module. Simply injecting the "@stripe_api.stripe_api" into your class is sufficient to open a connection. For example:

The goal of this module is to provide a layer of permissions to nodes that are published. It was initially created to restrict certain users from modifying a node once it has been published (or "approved") by someone with the ability to publish nodes.

Make a new Rule action available that will e-mail a Drupal user a Certificate node's PDF representation.

An implementation of Conditional Fields hooks to define example custom states/effects/conditions.

Extra formatter options for Field Groups:
* fieldset: set title display to visible/invisible/none (NB currently fieldsets don't use #title_display, no #title is set to NULL in both latter cases)

Module to add BEM classes to fields/entities based on a configurable array of field/entity/bundle names mapped to BEM classes.
Provides hook_bem_alter($bem_array) to view/alter the BEM classes.

TODO:
* blocks
* views?
* ...